281–290 of 519 posts
People who've made lots of git commits... have made lots of stuff.
Experience and knowledge is commensurate with ability.
Even though we say "lines of code don't matter, it's about the importance of lines of code."
Anecdotally, lines of code is a very good proxy for how much time you spend puzzling through the machine.
“If you’re the smartest person in the room, you’re in the wrong room.” I know saying this is easier than doing it, but; seek upward movement until you no longer feel like you're the smartest person in the room. I would also add, although it's purely personal opinion, that seeking a solution to loneliness through work is a surefire way to feel more lonely. You say you're big on self-improvement, but are you only focus…
But I agree with everyone else here: time to move to a bigger pond.
1. Pick an outside of work hobby… for me it was to teach myself electronics. Arduino, soldering, 3d printing , 3d modeling etc…
2. Remember using a computer is going to pull you down - I’m sure there are studies that show increased depression from using and being connected 24-7, I’m not saying disconnect - I’m saying be self aware and pick yourself back up. Live for the problem solving.
Hope this helps
I think you're an above average developer working at a below average company. This could be the root of all your problems. Nothing is more frustrating than working with peers you know aren't carrying their weight. Do you want to be an engineering leader? This is what you are, regardless of your official title at your company. Engineering leaders are judged by how much better they make everyone else. You may hear the…
I worked for a famous Japanese imaging corporation for almost 27 years. The pay was meh, the corporate overhead and B. S. was damn near unbearable.
But I worked as a peer with some of the finest engineers and scientists in the world, on a daily basis, and we respected each other (but often also wanted to strangle each other).
I was seldom the smartest person in the room (and I’m smarter than the average bear). It was humbling, challenging, and exciting.
I became a manager, and hated it. I was a very good manager, but spent my nights and weekends, coding.
Since leaving that company, I went straight back to coding, and I’m not as good as I was.
I’m way better.
I don’t really care whether or not I’m better than anyone else, but I find that I can usually meet any challenges thrown my way[0].
It seems that I picked up some good habits, along the way.
These days, most folks in the industry don’t want to have anything to do with me. I’m radioactive. It only took a short time to figure out that no one wants Pops on their team. I won’t go where I’m not wanted.
I’m extremely fortunate, in that I can support myself without earning a salary. I sought out people that want to help others, and have been working with them, for free.
It’s working for me. I’m not lonely at all, and I’m pretty motivated by the work.
[0] https://littlegreenviper.com/miscellany/thats-not-what-ships...
Interviewing elsewhere seems like the right thing to do. I'm confident there are environments out there where other engineers would challenge you.
It's possible that could be the case at my company, PicnicHealth. If you'd be interested in chatting, reach out (email in profile)
I thought I was “above average” in my area of expertise until I landed a job at BigTech coming from a 60 person company where my “specialty” was table stakes just to get a mid level position.
I use to always say with a point of pride that it never took me more than a month to get a job. Does that make me a 10x developer or is it because I only applied for no name companies until my current one?
Earlier quoted context omitted.
Eh, that is exactly what I don't want. Pretending I am this amazingly productive developer and my code is just trash. I just checked. In 2021, only two defects were created against my specific code changes. If I had to home into a weakness of mine is that sometimes I solve today's problem well, but don't think extensively about how tomorrow's problem in that space might look like. The struggle is between creating sim…
It's not about behavioural defects. It's that the _code_ is trash. It is unmaintainable and slows down all future changes, exactly because the person who wrote it didn't take the time to think about the future or even good architecture in the present. Every time I touch their code I have to almost redo their work because: - It's impossible to understand what is going on (For example when people load huge json or sql…
I'm speculating here but I think that you have some major hurt and pain in your past and something OP said is triggering the memory(ies). There definitely are (many) people in the dev world that do what you're accusing OP of doing, so I'm guessing you've been heavily burned by that (as have I). I actually moved industries to get away from that. In my case it was the Java (especially "enterprise" java) culture/ecosystem/etc, and things got a lot better for me when I wrote off my deep investment in Java and pivoted to C++ and Ruby. I would definitely advise to move around early and often, both company and tech stack. Try out startup life if you've been in big corp, or vice versa. IME startup life is a lot more prone to the "ship it fast" pressure that results in terribly unmaintainable code, so a big corp where you can work on a core product (core enough that it gets plenty of investment and appreciation but not enough that it's the number one money maker, otherwise the Eye of Sauron will be omnipresent and encouraging bad practices). Life is way too short to be miserable at work, especially in a field like ours where hold a ton of the cards.