371–380 of 510 posts
That's ... that's not at all how that works.
> Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all. Couldn't agree more
which is why leetcode makes no sense, as it focuses on premature optimization and writing the most advanced code possible which no freshman will be able to understand, at least not without dissecting it for a few hours first.
>> Qualities of a good manager share a lot of qualities of a good engineer. OK, you're drunk.
Really? This one aligns pretty well with what I've learned. It seems that the entire stack of people in software development is tasked with identifying problems and subdividing them in to smaller problems. This goes for coders structuring lines, architects structuring modules as well as managers structuring teams of architects and coders. The quality of a software engineer shines through all these layers.
> How do you know if you have a good [recruiter]? If they've been a third party recruiter for more than 3 years, they're probably bad. The good ones typically become recruiters are large companies. That's ... that's not at all how that works.
OTOH, my experience with same-company recruiters was that they merely existed to act as a simple filter and PR person. They didn't invest anything in me (the candidate) nor really examine if I was a good fit before I got passed further on up the chain.
Now that I really think about it, the quoted advice is pretty much a mirror opposite to my experience.
Earlier quoted context omitted.
Who hurt you??
I've personally witnessed friends doing this as a man. A bit sad, and certainly not true of all men, but it's not false.
Why is that sad? Have you ever heard of speed dating? Similiar concept.
Why does he hate pandas?
I assumed it was an autocorrect for Lamda
not a single comment in here addressing two of the most important points brought up by the OP. the redditors managed to do it constructively. while gender and racial politics are clearly orthogonal to the concerns of the average HN poster, the tech we build is imbued with them and we are responsible for the issues produced by the lack of their consideration. > There's not enough women in technology. What a fucked up…
If you care about this issue can you consider editing your first paragraph? It's likely to preemptively derail the discussion you're trying to get started.
> If people are trying to assign blame to a bug or outage, it's time to move on. This is one of my favorite excerpts. I once worked in a lab where we would have frequent catastrophic failures because there was never any disaster planning or contingency management plan. I personally triaged 3 such incidents alone or with people who happened to be there when the problem arose and attempted to disseminate some suggestio…
> When I first started, I was enamored with technology and programming and computer science. I'm over it. This is the saddest. One more soul taken by the shrinking of the hacker culture.
The other day, I started playing this game called TIS-100. The game simulates something like assembly programming and I had so much fun with it. Then I realized it’s been nearly half a year that I’ve actually written proper code for something (rather than a GitHub workflow script or account provision mechanism for testing framework) and built something that I was actually proud of. The love and passion are still ther…
They also have another game (the name of which escapes me right now) that is sort of like a bigger version of TIS-100, where you have to write code for microprocessors. I didn't get into that one -- it was a bit less pure and straight to the point compared to TIS-100 or SpaceChem, and one of my favourite things about those games is their fundamental simplicity and transparency -- but I've heard it is good too.
This, and the current “sober” posts on r/ExperiencedDevs, makes me think of Herodotus describing the way the Persians made important decisions - once sober, once drunk, and if the drunk and sober decisions were the same they knew it was a good one.
Reminds me of Hemingway's "Write drunk, edit sober."