HNHacker News
TopNewBestAskShowJobs

q7xvh97o2pDhNrh

1,813 karma · joined June 15, 2022

submissionscomments
q7xvh97o2pDhNrh··on Ex-Finance developers mock McKinsey's monitoring metrics
I clicked through to the linked McKinsey article [1] to see what all the hubbub was about, and I found this gem:

> For example, one company found that its most talented developers were spending excessive time on noncoding activities such as design sessions or managing interdependencies across teams. In response, the company changed its operating model and clarified roles and responsibilities to enable those highest-value developers to do what they do best: code.

The rest of the article is equally hare-brained. It's a sort of clueless management-consultant thinking that believes software engineers should be furiously typing all the time, and it entirely fails to understand that actual software engineering is about solving business problems.

Stuff like this really makes me wish I'd optimized for $$$ earlier in my career, and I only hope I can retire before this kind of absurd thinking spreads into real technology companies.

[1]: https://www.mckinsey.com/industries/technology-media-and-tel...

EDIT: Changed "MBA thinking" to "management-consultant thinking," in response to fair feedback below.

q7xvh97o2pDhNrh··on Googlers told to avoid words like ‘share’ and ‘bundle,’ US says
> if the year of the Linux desktop has finally come

No, I think that's next year. ;)

q7xvh97o2pDhNrh··on Skip the API, ship your database
Most of the Internet spent the last 10-20 years moving away from this because business metrics generally benefit from realtime updates and background autosaves. By and large, users expect systems to autosave their work-in-progress nowadays.

You might remember horror stories from the late 1900s when people would lose critical data and documents because they "forgot to hit Save and the computer crashed." Or, maybe you've never experienced this — because a couple decades of distributed-systems engineers and UX researchers made that problem obsolete.

So now we've... reinvented the Save button, but somehow needed a Paxos implementation to do it?

Everything old is new again, I guess.

q7xvh97o2pDhNrh··on Flexport CEO resigns a year after joining logistics company
That sounds rather grim; I'm sorry you had to go through that.

It sounds like it just underscores the reality that, no matter what process a team uses, there's no substitute for psychological safety.

q7xvh97o2pDhNrh··on Flexport is rescinding a bunch of signed offer letters
How long ago was that?

It's very different right now. Every team is starved for headcount. Job openings don't grow on trees these days — not even in FAANG-land.

q7xvh97o2pDhNrh··on Flexport is rescinding a bunch of signed offer letters
OKRs are a good thing. They just get poorly implemented and turned into a political stew.

I know that sounds like the No True OKR paradox [1], but the truth is that it's not even that complicated. [2]

Write down the outcome you want, and then write down a few measurable milestones on the way. Make the whole thing ruthlessly concise. Make each key result objectively measurable. Go execute. Get together as a team occasionally to debate the whole thing and see if it needs to change.

That's the whole thing. No need to over-complicate it.

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

[2]: https://www.youtube.com/watch?v=1ht_1VAF6ik, the whole system explained in 2 minutes by the OG himself

q7xvh97o2pDhNrh··on Flexport CEO resigns a year after joining logistics company
Do you mind saying more about "the choking out of candidness"?

I know they've got their "leadership principles" kool-aid [1] at the interview stage, but I always assumed that a seriously profitable and hard-working company (which they seem to be) wouldn't waste time mincing words.

[1]: https://www.aboutamazon.com/about-us/leadership-principles

q7xvh97o2pDhNrh··on A Company of One
Three months? Can you share any data or case studies around such a number? Part of me finds it unbelievable (and part of me really wants to believe).

From a look at the two books mentioned here, though, neither seem to clear that bar.

Zero to Sold is about FeedbackPanda, which took 2 years. (Still impressive.) And Company of One, from a skim, appears to focus on services businesses — totally reasonable to get to six-figure revenue and therefore seven-figure valuation, but not terribly interesting as product companies and fairly difficult to exit via a sale.

I'd love to see some case studies of the 3-month number. The more I think about it, the more possible it seems (with a fair bit of luck).

q7xvh97o2pDhNrh··on CT scans of coffee-making equipment
I don't know if this is the ideal takeaway. Otherwise, we should all prioritize making our products flimsier and more expensive.

I think it's just a straightforward failure of creativity — or, even more plainly, a failure to understand their customer. They had a great product, which led to a loyal following — why not expand into adjacent markets?

The cruel irony is that their product was related to something that's extremely disposable. Why not get into the business of coffee beans? Why not partner with interesting coffee growers? Subscription businesses have been huge for decades, now — why not offer consumers the ability to buy an espresso bean subscription to go with their Mokapot, thereby generating a reliable recurring revenue stream?

A glimpse at their Wikipedia page [1] suggests they never even tried to branch out from the small, comfortable niche of cookware.

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

q7xvh97o2pDhNrh··on Divide your life into semesters, even when you’re not in school
Naive question: Are there any such cities in the US that have all that and all the other perks you'd want from a city (active dating scene; diversity of food, people, culture, museums, restaurants; good public transit; good schools; etc)?

I've been trapped in the concrete-jungle part of SF for a while, and — while I do really want to escape to a better, greener city — it's oddly difficult to find an alternative. I wonder if NYC may be the only viable candidate.

q7xvh97o2pDhNrh··on Divide your life into semesters, even when you’re not in school
After much experimentation and many years of failure, I've surfaced two rules of thumb for myself that seem to be working lately:

(1) Write a monthly plan that's broken down by weeks, and then review/iterate on it weekly.

The weekly review alone risks having too small of a focus, so blending it with a monthly planning horizon has felt like a nice balance.

(2) Yearly planning is surprisingly useful, but it's best done as a solitary thing.

Most people view the whole "new year's resolution" thing as a cliché, and — separately — most people don't respond well to seeing someone else's ambition. Silicon Valley promises to be some sort of magical land where everyone's working on big things, but — same as everywhere else in the world — people largely respond negatively to seeing someone succeed (or even want to succeed) on a long timescale.

q7xvh97o2pDhNrh··on Slack’s migration to a cellular architecture
At least three obvious reasons might be:

(1) Raw scale might mean you just plain can't fit everything on a single t2.2xlarge.

(2) Different services (containers) might have different performance profiles, so you may want a few different types of machines around.

(3) You probably still want N+2 redundancy even within your single AZ, so this scheme should at least be upgraded to three t2.2xlarge boxes. ;)

q7xvh97o2pDhNrh··on What happened to Wirecutter?
I start by opening a few tabs with various search queries, some of which are usually scoped to Reddit or HN. That usually kicks open a few more tabs, and maybe some dedicated forums or Shopify stores.

Then the hyperfocus takes me, and I stray out of thought and time, and I wander far through hundreds of tabs. I become an expert on the multi-decade rivalries between vacuum cleaner manufacturers, the nuanced multi-dimensional calculus of coffee grinders, and the intricate supply chain dynamics of family-owned towel-makers.

And then I throw down my credit card, the stars wheel overhead, and every day feels as long as a life age of the Earth... until the UPS driver arrives. At last, I have my hard-earned morsel of capitalism.

q7xvh97o2pDhNrh··on Ruby's hash is a Swiss-army knife
This is a lovely overview. Hash is a great example of how delightful it can be to program in Ruby.

One more technique worth noting is the chained functional style of using Hash, which you can do in Ruby because Hash inherits from Enumerable. If you're prototyping a script to do some data-cleaning, this makes it easy to build up your pipeline and iterate on it. For example:

    foobar = { ...your data here... }
    foobar.map do |k, v|
      # ...
      # do some transformation here
      # ...
      # and then return the replacement key/value for this entry
      [key, new_value]
    end.select do |k, v|
      # do some filtering here, e.g.:
      is_foobarable?(k, v)
    end.map do |k, v|
      # ...
      # do some expensive transformation here on the smaller data set
      # ...
      [key, newer_value]
    end.to_h
(Note that you have to call #to_h at the end since the Enumerable functions will coerce the hash into an array of arrays.)

Now your code literally shows the pipeline that your data is falling through — and each of these steps can be side-effect-free, with no mutations to the original foobar structure.

q7xvh97o2pDhNrh··on Job Corps: free, residential training and education for low-income young adults
Plenty of people manage to make it to much later in life without connecting those dots for themselves.

About the most one could say about 25 is that it's when people's paths start to radically diverge, even amongst the group of people that were previously lumped together as "high achievers." So perhaps the subset of that group who are relatively low-performing — and yet, somehow, high in self-awareness — will wake up and start making changes at 25.

q7xvh97o2pDhNrh··on Successful room temperature ambient-pressure magnetic levitation of LK-99
> the handwringing you see on programming forums about the 'leetcode grind'

In fairness and compassion to that crowd, a lot of it comes from the fact that a modern interview for a coveted FAANG job often requires 1-2 LC Medium (or Hard) problems cranked out in 45-60 minutes. Depending on the company and the org, the overall interview loop may well be multiple such one-hour sprints.

It's quite a pressure-cooker of an interview setting. Given that, it's understandable why many people converge on memorizing and brute-force pattern-matching as their interview strategy — if they can just memorize enough, the odds are actually pretty decent. (And the payoff is not bad, either.)

q7xvh97o2pDhNrh··on Successful room temperature ambient-pressure magnetic levitation of LK-99
And punctuation, too.
q7xvh97o2pDhNrh··on Marijuana addiction: those struggling often face skepticism
> was there any point besides you feeling superior to other

If you don't like that as a motivation, I have some bad news for you about 99% of the entire edifice of human history...

q7xvh97o2pDhNrh··on Google abandons work to move Assistant smart speakers to Fuchsia
> They were all separate, and that seems crazy and inefficient.

From an organizational-design perspective: That's the whole point.

Decentralization means they can all move more quickly — each team can cater to the needs of its local customers. In moving quickly and solving local problems, they end up repeating some work. That's the price of velocity. Good local leaders should counter-balance this by creating informal forums for idea exchange and cross-pollination.

Sadly, overly-ambitious office-politicians see this happening, flag it as "inefficient," and roll the headcount up into a centralized team. Centralization puts an end to all the local ideas and excitement, instead routing it through a centralized committee that "plans" and "decides" which customers are worthy of how much innovation.

In a way, this is the pendulum of life at a big company. But in another way... this pursuit of "efficiency" sure seems like it explains a lot of why Google moves so slowly.

q7xvh97o2pDhNrh··on Twitter has officially changed its logo to ‘X’
It's all regurgitated and repackaged into tweet-size aphorisms, too. It's a sort of junk-food version of philosophy.

I feel like "Sapiens" and Eckhart Tolle cover a large percentage of what he's saying (though admittedly I haven't checked out his latest musings). I wonder if anyone's crowd-sourced a "top 5" of what the underlying worthwhile books to read would be.

Some brief searching turned up this "reading list," [1] though it looks a lot like one of those book-lists people make to show how they smart they are.

[1]: https://www.kevinrooke.com/book-recommendations/naval-ravika...

q7xvh97o2pDhNrh··on Ask HN: Do Agile 'Sprints' Benefit Software Developers?
The entire "Agile Manifesto" is less than 10 lines, and it's right here for free: https://agilemanifesto.org/

If you want the longer and more detailed treatment, that's right here too, and it fits in 1 screen: https://agilemanifesto.org/principles.html

That's the whole thing. All of the "sprint" and "scrum" stuff was invented as a way to pretend that software-engineering is like factory work. You'll hear these people talk about things like "holding engineers accountable" and "making estimates more accurate," which is an instant giveaway that they don't understand the fundamentally organic and ever-evolving nature of software-engineering.

The only thing that actually needs to be done is to write down clearly the business problem to be solved, the reason it matters, the proposed technical solution steps in order, and the rationale for the solution. Then, meet regularly to talk about it and update it based on reality.

But most companies can't handle that level of rigor in their business thinking — or the idea that engineers should have this kind of autonomy to solve business problems.

q7xvh97o2pDhNrh··on Fly.io Postgres cluster down for 3 days, no word from them about it
I admit I didn't run the numbers before posting that. But you got me curious, so I went ahead and did it now...

Render.com looks like [1] their "$0 + compute costs" plan would work out to:

  ∙ $25/mo for a single "Web Services" box of 1 CPU and 2GB RAM
  ∙ $20/mo for a single "PostgreSQL" box of 1 GB RAM, 1 CPU, and 16GB SSD
  ∙ TOTAL: $45/mo, and you're assuming they'll magically give you zero-downtime
Those are grim numbers, performance-wise, but let's use them as the standard and see what it'd cost in the scrappy AWS architecture I threw together in a few minutes:

  ∙ $12.10/mo for a single t4g.small box, which is actually 2 vCPU and 2GB RAM [2]
  ∙ 3x redundancy on that brings you up to $36.30/mo for compute
  ∙ $16.20/mo for an ALB [3]
  ∙ $11.52/mo for a single db.t4g.micro PostgreSQL box, plus $1.84/mo for the equivalent 16GB of storage [4]
  ∙ TOTAL: $65.86/mo for substantially more CPU, redundancy, and control, or...
  ∙ TOTAL: $41.66/mo for substantially more CPU and control over your infra, if you're willing to drop the redundancy
So it looks like it's pretty comparable in terms of raw dollars.

I'll admit there's a little more "devops" overhead with the AWS setup. Though I think it's not as big of a deal as people make it out to be — it's basically an afternoon of Terraforming, and you'd probably spend an equal or greater amount of time digging through Render's docs to understand their bespoke platform anyway.

(Also, once you contemplate bulk pricing for the underlying commodities, it's easy to see how companies like Render make a healthy margin, even on their low-end offerings.)

Anyway, I guess I've nerd-sniped myself, so I'd better stop here. But that was a fun analysis!

[1] https://render.com/pricing#compute

[2] https://aws.amazon.com/ec2/pricing/on-demand/

[3] https://aws.amazon.com/elasticloadbalancing/pricing/

[4] https://aws.amazon.com/rds/postgresql/pricing/?pg=pr&loc=3

q7xvh97o2pDhNrh··on Fly.io Postgres cluster down for 3 days, no word from them about it
Maybe just pick up 3 chonky EC2 boxes, set up iptables on each of them, have each one run a containerized version of your code that gets built and deployed from CI every time you push to Github, slap an ALB in front of it all, and call it a day?

And if you need state, then spin up a little RDS with your favorite SQL flavor of choice?

The CI deploy script could even bake in little health-checks so you can do rolling deploys with zero downtime. Depending on how fancy you wanted to get with your shell scripting, you could probably even make 1 of your 3 boxes a canary without too much trouble.

I'm realizing I haven't thought about this in a long time, since nowadays I just get to use the fancy stuff at work. Kind of a fun thought experiment!

q7xvh97o2pDhNrh··on Meta Tells Managers Promotions Will Be Few and Far Between
Abstractly, it seems quite reasonable — whatever gets measured gets optimized, and for years Big Tech has measured headcount as a metric of manager skill. Eliminating that metric directly tackles the problem of empire-building.

On the other hand, it's already difficult to retain talent, and a single good manager can be transformational for a team. Between this and the RTO shenanigans — both of which seem to be widespread across the tech industry these days — it's tough to see why talented managers would stay, let alone put in hard work.

Overall, it feels like an incomplete solution. If we as an industry are going to move away from headcount as a professional growth metric, we need to have some other, more direct way of measuring the business impact a manager delivers so we can reward that.

Standing up and telling a roomful of high-leverage hires that their career trajectories are frozen for 2-3 years is probably not a winning strategy by itself. If I were a hungry startup founder, I'd read this as an invitation to ramp up recruiting.

q7xvh97o2pDhNrh··on CEO Announcement to the Netlify Team
Respectfully disagree. It's important to explain why, and he does that in a standard 3-point structure without getting too carried away on the hype train. It could be worse.

Also, this part is worth emphasizing:

> For those amazing Netlifolk that are leaving us today, our team is... waving [sic] the first year stock option cliff for newer employees, and extending the exercise period to 7 years.

This is a classy move. They didn't have to do this, but they did. Layoffs suck, and no amount of wordsmithing on the email is really going to make a huge difference. It's worth noting and encouraging when companies at least take the time to do something for the people they're letting go.

I fully agree with you on one thing, though: the word "sorry" is conspicuously missing. A little more ownership would go a long way.

q7xvh97o2pDhNrh··on Instant Messenger History: Lessons for the Threads Era of Social Media
My memory is hazy of those years, but I do think it was a bit different.

IIRC, G+ was a defensive maneuver. G was terrified of FB, who was executing successfully on many fronts and putting pressure on advertising revenues. And so G tried to make G+ happen.

By contrast, in this case, Twitter keeps shooting itself in the foot. (I guess that's what happens when you lay off huge swaths of the company and demand that engineers print out their code on paper.) So Threads (and others) are moving into the vacuum that's been created.

So things right now feel like much more of a competitive land-grab, and it's not entirely clear who's going to win (or even why/how they'll win, or even what the victory conditions look like).

q7xvh97o2pDhNrh··on Bard’s latest update: more features, languages and countries
Could you share some new ways you've found?

I'm in the cohort of users whose usage flatlined. I had a lot of fun asking it all kinds of stuff for a while, but — sometime around all the hubbub of whether or not OpenAI uses your interactions as training data — I just stopped entirely.

q7xvh97o2pDhNrh··on Bard’s latest update: more features, languages and countries
> it went on an unprompted rant about how I should speak to it "politely".

Can you share the prompt that led to this? I agree this sounds pretty disconcerting.

q7xvh97o2pDhNrh··on AMC Says More Than 20k Have Booked 'Barbie'-'Oppenheimer' Double Features
> they didn't cost too much to make

A quick search suggests each had a $100M budget, so it's worth noting they're not exactly cheap. They'll still need pretty big opening weekends to turn a healthy profit.

q7xvh97o2pDhNrh··on Feature Flags: Theory vs. Reality
> I've at times been told that tech debt is fine because products only last 3-4 years before a replacement gets made.

Translating from corp-speak, whoever said that probably meant: "I plan to get promoted before we need to pay this tech debt down."

← PreviousPage 3 of 11Next →