Quoted post unavailable.
Tell HN: The loneliness of a pretty good developer
311–320 of 519 posts
Re: Tell HN: The loneliness of a pretty good developer
#312Quoted post unavailable.
Re: Tell HN: The loneliness of a pretty good developer
#313Socializing after isn't easy, do you DM someone, follow up, schedule a time to talk? That's unreasonable.
My latest startup Vibehut.io can help, here's an open video room for Developers, join when you want to chat, screen share your work, shoot the shit
w/e you want, here's the link, login with Twitter.. do with it what you will
Re: Tell HN: The loneliness of a pretty good developer
#314Earlier quoted context omitted.
Quoted post unavailable.
Quoted post unavailable.
You even have a good point. I'm sure many SV companies are filled with politics and good deeds aren't often rewarded.
But being an asshole doesn't make you more right. It just makes you an asshole.
Re: Tell HN: The loneliness of a pretty good developer
#315Re: Tell HN: The loneliness of a pretty good developer
#316Re: Tell HN: The loneliness of a pretty good developer
#317Earlier quoted context omitted.
I can go really deep talking about this, so I will just write my personal system pointers that I keep by my desk. Iterate fast > perfect Write it down to relieve cognitive load. Uni-task (focus on one thing at a time) Prioritize and execute. Solve problems by: a. Invert - improve by subtraction b. Decision trees - compare outcomes, reduce load There are two types of decisions. Hard choice (A vs B), or multiple factor…
n terms of actual code reminders I try to make it work, make it right, make it fast. I also try to do always, then inhibit, then ignore cases that don't apply. Minimize if statements to have consistent execution. If a function is called from one place I will inline it. From multiple places I will try to see if I can have it happen in one place so I can inline it (plus it's an optimization thing). For complex calculat…
Re: Tell HN: The loneliness of a pretty good developer
#318If you joined a new project where someone else had written 80% of it, it would take you years to catch up to their productivity; if they were controlling and continued to write 80% of everything, it would be impossible. The next step in becoming a better engineer for this project is figuring out what you need to do differently for everyone else to be more productive; for example, if other people are pushing bugs, you need to add tests to make that impossible. If people take a long time to ramp up, you need to refactor the code so that someone doesn’t need to understand -all- of it to start contributing; you might also need onboarding docs.
The next step in becoming a better engineer generally is to switch teams and learn new skills. If you enjoy hard technical work, miss feeling challenged, and genuinely feel like you’re a much better dev than average, try switching to a hard field that’s new to you: distributed systems, ml, performance engineering, etc.
Re: Tell HN: The loneliness of a pretty good developer
#319“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…
Re: Tell HN: The loneliness of a pretty good developer
#320“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…
And you realize that person spends their life handing out wisdom which consistently just falls on deaf ears.
It's an empty journey with an unsatisfying end even if you make it to the top.
The money's great, but if you are smart enough to be constantly walking into bigger and better rooms, you should also be smart enough to realize there's diminishing returns on personal wealth but diminishing supply on personal time.
Sometimes the best strategy in winning a game is not to play.