3 ms·
I would say to forget about problems involving algorithms and try to build projects with a very concrete use case. Maybe you should just quit trying to be a pro
by soneca 8y ago
I would say to forget about problems involving algorithms and try to build projects with a very concrete use case. Maybe you should just quit trying to be a programmer that can pass a whiteboard interview at Google, and start trying to be a programmer that can provide usable software that solves a problem for a regular company.
- leetbulb 8y agoTotally agree here. You'll have no issues in your career if you can write software that increases revenue for a company. Sure, being able to visualize and implement data structures and algorithms is extremely useful, but I wouldn't say it's absolutely required to enter the industry. Hell, when I first started professionally, I couldn't tell you the difference between a binary tree and b-tree. If you're passionate about software development, it'll come naturally.
- Tmp1234 8y agoIf I was only interested in programming to become a google worthy programmer, would you say I have enough evidence that I should quit?
- soneca 8y agoYes
- Tmp1234 8y agoCould you expand a little? It's a big life decision I would be making.
- soneca 8y agoIf you created a category in your mind that is "Google-worthy"* developer, that prioritizes above all specifically the niche of Software Development that your struggling with, I believe it is a sign that you should not keep trying to pursue this specific goal. But I do believe you should try to be a software developer at all before you decide what exactly what kind of software developer you should be for all your career. You have never worked with software developer and you are willing to consider only one aspect of it "worthy"? *A comment, google-type whiteboard interviews does not mean that they do select better software developers. It is a bias, not necessarily a bias to the best ones.