Can a technology consultant become a software engineer
Categories: TECHNOLOGY
Technical Consultant
1. Examine UX criticism report from a client study directed last month with client/item proprietors.
2. 20% of examiners revealed that in processing plants network conditions are terrible and they can not occupy reports progressively. They need to make a note on paper and type it up on the site after the visit again in the right configuration.
3. The client consider this overt repetitiveness to be an issue and contacted me to "Track down an answer".
4. We did a great deal of digging the entire day, gauged the upsides and downsides of each and every conceivable arrangement.
5. Following 2 days and 20 espressos, gave them the possibility of a helping PWA(Progressive Web App). It tends to be introduced locally and they needn't bother with a web association with open the real site.
6. I chipped away at a POC demo for the following multi week and concocted a fake 5 field report structure mounted on a PWA with few approvals and business rationale empowered. Here, you can compose a report even disconnected alongside photographs from the telephone camera and when you recapture association it will match up to the fundamental data set.
7. I began to do cost, practicality and viability examination with the business administrators after the fruitful demo and helped with approving the last proposition.
8. When the course of events was supported, I began organizing with the advancement lead on the execution plan for this component.
9. The circle begins with the dev and qa groups until the last work is finished, guaranteeing the vision for the arrangement never gets redirected.
Senior Software Engineer
1. Hit 3 straight coffees without sugar.
2. I sit in a gathering with the above specialist and examine the component alongside the ultimate objectives.
3. Since I have a superior ground report, I educated him about the intricacy regarding carrying out the component in this site and proposed changing a few overheads in the course of events for preparing one designer in PWA particulars for two or three weeks.
4. I likewise concentrated on the arrangement till 3 AM and found two or three other specialized obstacles wrt to the execution in this particular task.
5. After everything was tended to, I began investigating the libraries and combinations we'll require for this component and chose the best toolchain for the gig.
6. I separated this work into 3 runs, each having 15 days and placed nuclear expectations in each staying away from any cyclic conditions.
7. In the wake of disseminating work among dev colleagues, code commits fired springing up and presently I invest the vast majority of my energy guaranteeing best practices are followed and the element codebase is adaptable and bugs are not marked as highlights. Occasionally, I likewise put in two or three hours coding a few basic pieces of this element myself.
8. After each run, I and my advisor companion sit together and examine what we accomplished and the arrangement of progressing work with the proposed arrangement.
Conclusion
The above case study would have given you a practical and first-person look into what work each of those roles does and in the project lifecycle where they are most active in. A consultant is more in touch with the business, whereas engineers tend to incline towards the product. The general rule of thumb as per me will be:
Choose Consultant line if you have/aim for diverse technical and practical knowledge. It allows you to decide what’s best for the business, unchained from a particular technology.
Go for a Software development role if you love converting a solution on paper into a robust and clear codebase. It requires more in-depth knowledge of the specific technologies and know-how.