HNHacker News
TopNewBestAskShowJobs

q7xvh97o2pDhNrh

1,813 karma · joined June 15, 2022

submissionscomments
q7xvh97o2pDhNrh··on CD sales growth outpaced vinyl in the first half of 2026
> And here I am driving a 2003 Golf with a tape deck (and CD player).

That sounds wonderful.

There was a brief, magical moment in history when cars would come with AM/FM radio, a tape deck, a CD player, and an aux port so that you could plug in audio from every other device that humanity would invent for the rest of time.

It feels like the most fleeting of moments, and it was so long ago. Maybe it was just one summer afternoon in the early 2000s.

Anyway, I think we've largely been going downhill since then. For whatever reason, humanity achieved a lovely little peak of engineering, and then we immediately abandoned it for worse options.

q7xvh97o2pDhNrh··on M4 MacBook Pro
Absolutely incredible to see Apple pushing performance like this.

I can't wait to buy one and finally be able to open more than 20 Chrome tabs.

q7xvh97o2pDhNrh··on Ask HN: Is patio11's salary negotiation guide relevant in today's market?
Any thoughts on root cause from your perspective?

I've been on the other side of the table recently, and I agree it feels like a buyer's market. But it still took a while to find good candidates, and a lot of candidates showed up to interviews weirdly unprepared on even the basics.

If it's a drought for you, then I'd have to add: It seems like an especially weird drought, as well. Supply and demand seem to be doing odd things.

(And, for the spectators of this comment thread, I can confirm: Yes, 2 people with 3 anecdotes each is enough to speculate wildly about an entire industry.)

q7xvh97o2pDhNrh··on Software Engineering Body of Knowledge (SWEBOK) v4.0 is out [pdf]
> The IEEE has been riding this horse for a very long time

Well, there's your mistake right there. You're supposed to be riding an ox.

All this talk of oxen and horses got me curious about the PDF, so I went and took a look. It's really far worse than you've described.

I couldn't stomach it for too long, but here's some highlights:

(1) The first ~65 pages are about "requirements gathering." Page 60 offers up this gem of insight:

    Priority = ((Value * (1 - Risk)) / Cost
(2) The next hundreds of pages go through topics in sequence, like "Architecture" and "Design" (who knew they were different?). Naturally, "Security" is slapped on several hundred pages later.

I couldn't make it through the whole PDF, in all honesty. But I'm quite certain the soul of software engineering is nowhere to be found in there; they've eliminated it entirely and replaced it with stamp-collecting and checklists.

q7xvh97o2pDhNrh··on Five days a week in the office? Forget it
> I would rather be a poor entrepreneur/freelancer than wealthy salaried employee. And office isn't really the factor, but other things, like freedom.

To add a data point that will sound snarkier than it is:

I used to say very similar things. It is a really wonderful sound bite, and you can get together with all the other starving founders to say things like this to each other.

Looking back on it, I think this philosophy is actually a really important part of the startup-industrial complex. If you can just make it "not cool" to go get a job, and starting a startup is all about "freedom and adventure," then it becomes really easy for VCs to normalize things like "founders paying themselves subsistence salaries." That means the pipeline of new startups will increase in quantity and decrease in unit-cost -- which is exactly what the VCs want.

What they won't tell you about, if you want to chase the founder dream, is the opportunity cost. It turns out that maxing out your 401(k) is pretty great, as is having an infinite supply of sparkling water and spending your days building software with a whole bunch of other brilliant people.

I'm still not going to RTO, though. That part is just dumb, and I think every serious company that truly values engineering productivity will agree.

q7xvh97o2pDhNrh··on Software Engineer Pay Heatmap Across the US
The "outliers" are the companies paying these insultingly low salaries for technology development. That's why there's so much low-quality software in the world.

FAANG (and a few FAANG-adjacent) companies are the only ones paying close to decent wages, and even they've been making frankly egregious cuts to their protein-bar budgets lately.

Let's not sit around manufacturing skewed datasets that give people the wrong idea about what software engineers should get paid.

q7xvh97o2pDhNrh··on Social Initiation
> I don't think the author is sympathetic to autistic people

I think it's actually the exact opposite.

This reads to me like a very kind sentence. It can be very helpful to spell things out like this for such an audience. It is clear, simple, and direct.

I'll also note the sentence doesn't contain any sort of added emotions or judgment. (For example, the author could have made it worse by saying "If you decide to engage in" rather than "If you engage in," as it's currently written.)

So it really is just a straightforward statement about things that are usually never discussed at all. And, even better for this audience, the information is provided plainly, in a safe setting, with time and space to process things.

q7xvh97o2pDhNrh··on The Legend of Holy Sword: An Immersive Experience for Concentration Enhancement
Forward/backward in which dimension? There's at least three or four to sort out.
q7xvh97o2pDhNrh··on How we communicate signals seniority
Counterpoint:

"When art critics get together, they talk about form and structure and meaning. When painters get together, they talk about where to get the best turpentine." (Picasso, supposedly [1])

To be generous to OP, I think their point is about how to communicate in an elevator pitch, or a resume bullet point, or the first few minutes of an intro call. And in those contexts, OP is pretty reasonably correct.

What it comes down to is details.

The person citing numbers about growth, hiring, or whatever is proving they know the details of the work. And that's a great start.

The next step for the interviewer comes in following up to find out whether they actually know the details of how the work was done, why it was done that way, what was good or bad about how the work was done, and why it's good or bad.

A good follow-up question would be something like: "Great, please walk me through the story of how you took ${METRIC} from A to B, what you think went well, and what you think went poorly." That should yield a solid 10-15 minute (or more) discussion where the executive candidate can prove they have the ability to handle both minute details and grand strategy at the same time, as well as the discretion to know when they're supposed to be doing which one.

Failure to do this on the part of the interviewer is how a company ends up with so many sub-par executives. And a failure on the part of the executive to push themselves in this way, in the first place, is how our industry has ended up with so many sub-par executives.

[1]: https://quoteinvestigator.com/2016/10/20/turpentine/

q7xvh97o2pDhNrh··on Online Dating
> My female friend once experimented by putting up a picture of a shoe as her only dating profile. She still received many likes - some of them paid Super Likes.

Well, obviously. Every guy wants a woman who's got some depth to her sole.

q7xvh97o2pDhNrh··on DEF CON's response to the badge controversy
There's also several more classes of B.S., for what it's worth.

An exaggerated/anonymized version of a recent one I got, from an otherwise-really-strong senior engineer: "Of course when I said we would put a button there, it also meant we MUST build an entire UI framework from scratch, with full test coverage for the entire thing!"

...actually, that's not even that exaggerated. Shipping software at big companies can be unreasonably difficult, sometimes.

q7xvh97o2pDhNrh··on Apprentice, Journeyman, and Master: The Medieval Guild (2018)
> My own feeling is that guilds of all sorts prioritize exclusivity for the purposes of bestowing power on some select few. As the article states "Master’s were few and far between".

One possible reason could simply be there's a lot more future impact to granting someone the final title. If you proclaim someone a "Maestro of C++," then suddenly all the other C++ laborers will get a clear signal that whatever that person is doing is implicitly also what they should do, if they want to move up the ladder.

Beyond that, the top jobs usually comes with required work to train the next generation. So this person would heavily contribute, both implicitly and explicitly, to the future of the C++ guild.

Considering that impact in combination with how hard it would be to undo the decision, it's not surprising that many organizations might be cautious about deciding to hand someone that title.

> clear guidelines, training, testing and certification.

This makes sense, too. For any organization that wants to stay in the business of handing out these titles for the long-term, meaningful transparency is a good way to go about it.

q7xvh97o2pDhNrh··on "We ran out of columns"
...and whoever did that "accidentally" when they had to leave around lunchtime on Friday was, presumably, celebrated as a local legend.
q7xvh97o2pDhNrh··on My programming beliefs as of July 2024
Yeah, this one was surprising to me, too.

It's not even that complex to do correctly. Usually, it's about 30 seconds of work to just go to https://http.cat/ and pick out the relevant cat.

q7xvh97o2pDhNrh··on The Later Years of Douglas Adams
> a tower of a man, confident in the face of chaos and uncertainty, purely through force of word and logic

I've been the same, ever since I learned to always keep a good towel around.

q7xvh97o2pDhNrh··on Dear AWS, please let me be a cloud engineer again
As a person replying to your comment in the era of generative AI, I'm inclined to agree the hype is a bit much, even considering how impressive the technology can (sometimes) be.

Another big area of hype is "prompt engineering." That one seems to have calmed down slightly, but for a while, there were large swaths of the Internet who were amazed that the set intersection of "talk like a decent human being" and "be precise in your communication" could generally lead to good results.

In many ways, "AI" right now is magic marketing sprinkles that you can put on anything to make it more delicious. (Or, if you're inside a big company, it's magic prioritization sprinkles.)

q7xvh97o2pDhNrh··on Why not just embed Neovim?
One time, I paired with a guy that used `R` all the time.

It was an eye-opener for me, too. I use `R` a little more often ever since then, but -- like a lot of others here -- my mental model defaulted to more of a `cw` approach.

Maybe there's just two types of vim users. This could be the latest new Silicon Valley personality test.

q7xvh97o2pDhNrh··on Pre-Work for Setting OKRs
> the mission is to make money and the vision is to make more money.

This is just fine, but it's not enough.

The purpose of writing a proper mission and vision is to say something about how. There should be some coherent strategic guidance, some notion of where the company is and/or wants to be in the marketplace or in customers' minds, and so on and so forth.

If you have that (and it's actually backed up by reality), then the OKRs emerge organically across the portfolio of investments the company is pursuing. Land N more deals with this existing customer segment, experiment with new features in pursuit of that other customer segment, staff a team to ensure customers aren't lost for reason X or Y, etc.

The real magic, of course, is that every person in the company can then make a clear statement about how they're contributing to the broader mission and vision of the corporation. When it all lines up, it really is a beautiful symphony of capitalism.

q7xvh97o2pDhNrh··on What factors explain the nature of software?
What you really need to do is schedule daily status meetings, a longer weekly status meeting, and -- this is the real velocity trick -- monthly OKR reviews as well as quarterly slide presentations.

It's important the slide deck be polished for all the people who want to come learn about the project, so it makes sense to spend at least a month preparing it.

And the neat thing is that all this work will get you lots of suggestions from executives about how you could address all the velocity issues that your project seems to have all the time! So you'd better budget 2-4 weeks after the presentation to follow up, have stakeholder meetings, and make sure everyone really feels heard.

With just these few simple techniques, you too can get your engineers moving at the blinding speed of an average FAANG engineering team.

q7xvh97o2pDhNrh··on Show HN: I created an app for you to be a more unpredictable romantic partner
> If they didn't think of getting you flowers themself (and had to use an app), is that real?

I did confess to my girlfriend once that I'd never thought of getting her flowers, and that every time I had bought her flowers in the past was actually just the output of a Chinese room. [1]

She said it was fine, and she liked the flowers either way.

[1]: https://en.wikipedia.org/wiki/Chinese_room

q7xvh97o2pDhNrh··on 'Irresponsible' to ignore consciousness across animal world scientists argue
> people with internal monologues might only make up 30%-50% of people

It's incredible to imagine there are people out there just thinking in language as they go about their lives.

I wonder how it must work. Are they literally lining up one word after another in their minds? I guess it has to work that way to feel like some sort of "consistent internal monologue"?

At scale, though, imagining a roomful of people thinking in single-threaded monologues does explain a lot about why some teams take forever to get anything done.

q7xvh97o2pDhNrh··on What to do when an airline website doesn't accept your legal name
> There are many variations out there (any authoritative?)

No, believing there's an authoritative list is one of the falsehoods programmers believe about falsehoods programmers believe about names.

q7xvh97o2pDhNrh··on How Often Have You Seen Mostly or 100% AWOL Managers?
Oh, man, I was hoping this thread would be about managers who have mastered the art of time management and are doing their jobs in a few hours per week.

One of my old managers had it. I would rarely see the dude -- except for once or twice a month, when we'd happen to be in the same meeting. He'd wait until the last bit of the meeting, and then he'd come in -- calm and measured -- with a comment that would blow everyone away. While everyone was nodding at what a good point it was, he'd disappear, never to be seen again until next quarter.

Meanwhile, I'm over here working a steady 50 hours/week and barely keeping up. Most weeks are wall-to-wall meetings, combined with a few over-caffeinated nights writing up some doc or another, and then it's a stumble into the weekend with just enough time to recover and start the whole thing over on Monday.

I'd like to hear from those kinds of AWOL managers. I have no idea how they do it.

q7xvh97o2pDhNrh··on Suppressing boredom at work hurts future productivity
I think there's a caveat with the current market.

Many Big Tech companies are in a phase of pre/post-layoff hunger games. Meanwhile, more and more AI startups are appearing, with lucrative-looking equity packages.

In both cases, a pragmatist could reasonably conclude that "working hard to keep the high-paying day job" is a better strategy than "going into the jungle and start a startup."

q7xvh97o2pDhNrh··on The Montreal problem: Why programming languages need a style czar
> my response was: i duplicated an existing structure and made mine look exactly the same. i agree that proper indentation would be nice. but if i did that, my structures would look different from the original. i could clean up the original too, but then the diff would be harder to read because it would contain unrelated changes.

The idealist part of me wants to say: Clean up the original code, submit that as the first diff, then rebase your additions on top as a separate diff.

The pragmatist part of me recognized long ago that a lot of software engineering now is like what you describe. The days of elegant, carefully-maintained codebases where someone sweated over every semicolon are long gone.

q7xvh97o2pDhNrh··on Why are most sofas so bad?
The Eames lounge chair is a reasonable solution to this problem.

(It probably invokes other stereotypes. I don't really know, but either way, you'll be too comfortable to care.)

q7xvh97o2pDhNrh··on Leadership is a hell of a drug
There's definitely something a little weird about people who proclaim themselves a "Leader" on their LinkedIn title.

I can't even imagine how that happens. Did they wake up that day, intending to do that before they even opened their laptop? "Today's the day!" Or, were they just dropping by the Edit form, when they were struck by such a brilliant idea?

Every time I see it, I just hear Tywin intoning the same old lesson:

"Any man who must say 'I am the king' is no true king."

I guess it sounds a little less dramatic when you swap in "Product Leader" for "king," but I think the point still holds.

q7xvh97o2pDhNrh··on Certain dogs are capable of learning the names for more than 100 different toys
> More impressive still, was she would be able to learn new toy names through inference. I'd come home with a new toy turtle, hide all her toys, say "go get your Turtle!", and she'd come back with the new toy.

Is it possible that she already knew about turtles before, though?

In that case, she might just be running a rehearsed routine. You know, a shell script.

q7xvh97o2pDhNrh··on Becoming a dungeon master for an interview
Not very well, in all honesty.

The function name is pretty misleading, since it looks like a constructor. Even if it's not a constructor, the functionality is pretty far away from the name you've chosen, so it's not a compelling API design either way. How would others use this function? How is this name self-documenting? The decision here is lacking consideration on all fronts.

Also, while I don't immediately recognize the exact language, the style looks off too. The function wetpaperbag is declared in all lowercase, but inside it's calling a function Quit that's capitalized? And, whether this particular language is camel-casing or snake-casing, it's clear that "wetpaperbag" isn't going to pass linting either way.

Overall, strong no hire. Next.

(/s... but only mostly, since the GP's point is that you actually can get a lot out of just asking simple interview questions, which I think we've helpfully proven out here)

q7xvh97o2pDhNrh··on Bard is now Gemini, and we’re rolling out a mobile app and Gemini Advanced
> The more detailed my prompts are, the more errors GPT tends to make. I use it as a partner to discuss implementation ideas, before I start coding.

This is interesting; I do a third thing that's the exact opposite of both of you.

I generally know the architecture I want, so I just slowly spoon-feed it to GPT-4 and have it build each of the components with the right interfaces to fit together. Usually, building each component requires a few rounds of hand-holding it through various refactoring. Its first draft of code tends to be, for lack of a better description, totally lacking in any creativity or elegance --- generally bland, insipid, and mundane stuff.

But it'll gladly take refactoring directions to get it into shape, so it's still very quick to get a whole bunch of components written up. Then I just glue everything together on my own. And the whole experience is still way better than writing a bunch of boring boilerplate code by hand.

Page 1 of 11Next →