5 ms·
There are numerous schools of thought on programming. For example, I've seen those who are interested in leetcode, algos, and the like. I remember this one tim
by mfer 6y ago
There are numerous schools of thought on programming.
For example, I've seen those who are interested in leetcode, algos, and the like. I remember this one time where management wanted to have JS/front-end devs answer questions about C and b-trees. They couldn't find anyone to make it through the whole interview process. The problem was that people who could handle the C and b-trees couldn't cut it at the JS questions that came later. The JS devs never got passed the C/b-tree questions.
There is a culture of elite knowledge and a club around that. Some are into the school people have degrees from and that kind of thing.
There is another side of it that's about the ability to use code to problem solve. I remember meeting this senior engineer that customers used to constantly request by name. He was one of the most senior levels at the company. I later learned that he had no degree. He had a ton of hands on knowledge and understood the technology from years of working. He learned it like a skilled trade and he was valuable to everyone involved.
There are places where both types of folks can thrive.
I personally go after the problem solving type situations because I don't like forms of elitism and I really like solving problems.
Don't look at the leetcode space and Google mentorship as the whole realm of software jobs. There is a lot more out there and many very successful people doing other types of stuff in software.
- sandrom927 6y agoagree on the whole elitism notion. it is about time we abolish that :)
- the_only_law 6y ago> I personally go after the problem solving type situations because I don't like forms of elitism and I really like solving problems. I used to be like this as well, till I noticed the people solving the types of problems I wanted to work on we’re either guarded behind these leetcode type interviews or something much more difficult to “fake until you make it”.
- mfer 6y ago> “fake until you make it” I don't like this idea. I prefer the idea of mentoring and people constantly learning. Faking it is kind of like deceiving until you figure it out. People should be mentoring and teaching each other. This levels up the people around us. > I noticed the people solving the types of problems I wanted to work on we’re either guarded behind these leetcode type interviews or something much more difficult This is a real thing. Sometimes you need a foundation in a hard problem that is often taught in some university courses. There are some hard problems here and people look for that. Sometimes it's math skills or specific algorithms. Sometimes the people working the hard problems artificially add levels to their processes to keep clubs exclusive. Most software isn't these hard problems. 99.9% of software is not these hard problems.
- QuitProgramming 6y agoDo those other jobs have the prestige, benefits and pay of Google though?
- UncleMeat 6y agoNot most of them. But so what? Your goal is to retire early. Why do you need to start at insanely high pay for that? Make 120k for a while (plenty of money to save well) and make this a longer term goal rather than an immediate "fuck it, I failed so the entire industry must be full of idiots".
- QuitProgramming 6y agoWhere are the non-FAANG, non-leetcode guarded 120k entry level jobs?
- gt565k 6y agoYou are chasing the wrong thing. There are plenty of companies where you'll solve better problems than at Google and have more freedom to solve problems your way, and they pay well too. Chasing money is not going to get you far. Focus on skills.
- sjcoles 6y agoEven if you can solve any whiteboard problem a company can throw at you your attitude is so off putting, even just via text, that I am not surprised you are getting no hits. Instead of getting shit done you'll complain, blame, and stall the team. Notice how nothing in this thread is your fault. Every single problem is on another person our outside force. No one will pity you, doubly so in a highly technical team. It's just not part of the culture. Take it or leave it.
- QuitProgramming 6y agoI'm not sure how you are coming to the conclusion that I take no responsibility. The whole point of my post is that I am not good enough. That's a pretty damning criticism of the self. I only blame others in the sense that they highly contributed to me not being able to see that. If all my takeaways were personal, I would have no reason to post this. I think you just don't like how I sound and aren't paying attention to my actual words.