HNHacker News
TopNewBestAskShowJobs

hnthrow289570

144 karma · joined March 3, 2024

submissionscomments
hnthrow289570··on Story points are pointless, measure queues
Non-developers might have to learn something about development so they can push back on inflated estimates, which honestly would be helpful to everyone.

If I quoted you $1,000 to unclog your kitchen sink trap, you'd call bullshit because you can probably find out how easy it is to do that. Likewise, if I quote you 13 points to add a generic error toast message because a POST went badly, you should call bullshit on that too.

hnthrow289570··on Story points are pointless, measure queues
The points are needed because it's convenient to do reports based off of it. If we used estimation language such as "easy, medium, hard, dummy-thicc" they'd still need to assign points to those labels so they can do math on reports and graphs to watch your performance

The biggest sin of course is then trying to predict velocity, but the consequences of that usually just make people doing the reporting look silly for no reason. I think even the slow developers rarely get fired, and you also get nothing for clearing more story points than other developers.

No bonuses for higher velocity is the real reason no one takes it seriously.

hnthrow289570··on Boeing to plead guilty to criminal fraud charge stemming from 737 MAX crashes
We should certainly do something about CEOs being in charge of large multi-billion dollar companies, rarely having direct consequences, and still being rich. It is currently reasonable that a CEO might not know everything when something happens the first time in a huge company. We shouldn't have only one person responsible, but likely a group. This is more important in safety critical industries, but less so for something like a luxury goods company, so you wouldn't want to force every company to this structure.

This is currently an advantageous single point-of-failure for companies and CEOs, and the advantage grows the more safety critical the industry that they're in. The company structure prevents any real responsibility except when the crime is blatant (like the CEO was recorded or wrote down something).

hnthrow289570··on The Software Crisis
I think this might be premature if you're trying to apply this to how the world makes money with software. There's too much of the economy that depends on adding another abstraction layer to make money, so you'd need to rewire that as well unless we just want to break things. You'd eventually have to tell a business "no" because they're +1 abstraction layer above the limit.

I think most of us realize that working at corporate is still a necessary evil as long as we need to pay for stuff. Frankly that sector can burn because they've been taking advantage of developers. Most of the money goes to people above you, performance bonuses are not the norm, etc. We shouldn't be actively trying to give them improvements for free because of this behavior. Let them follow the hobby/passion projects and learn these practices and limits on their own.

hnthrow289570··on AI's $600B Question
Yeah up until Mt. Gox exploded and maybe a bit afterwards

After that it started really getting its scammy, investor-only reputation

hnthrow289570··on AI's $600B Question
The only upside is state-level minimum wage increases. The federal minimum wage is still a complete joke at $7.25 an hour.

But there's bigger fish to fry for American politics and worker obsolescence is not really top of mind for anyone.

hnthrow289570··on Do I Regret Being 'Just' a Software Engineer?
Coasting is fine in a sane company. Coasting is a sign of competence IMO as long as your work is also getting done and things are fairly estimated. We should get to coast because we practiced enough to be good at our job.

There's way too many jobs where the only reward for finishing your work is more work.

However, I don't think hacker or punk rock culture can make a come back here because there's too large of a pool of people willing to work even for underpaid tech jobs (since it's often a relatively a lot of money for them)

hnthrow289570··on At 50 Years Old, Is SQL Becoming a Niche Skill?
People are spread too thin with their skills already, so it's no wonder they don't want to learn yet another thing (especially if you aren't the one signing their checks). The databases can be forgiving and EXPLAINs are not easy to interpret correctly for people who don't know databases that well.

A proactive solution of hiring a DBA to build things along with the FE/BE developers will likely never get traction due to costs. Businesses regularly put off performance and optimization until later and they still make good money in spite of that.

hnthrow289570··on Tech CEOs are hot now, so workers are hiring $500-an-hour fashion consultants
I love how we beat down tech workers' self-confidence and called them weird, and now we're charging out the ass for a button-up, jeans, and sneakers to take advantage of that of that vulnerability.

It would be different if the entire fashion and clothing industry weren't completely terrible about exploiting labor and doing stupid things like selling ripped T-shirts for hundreds of dollars.

I look forward to never judging anyone based on the clothes they were just so I can justify my own purchases and insecurity.

Cheap jeans and T-shirts for life.

hnthrow289570··on Neofetch developer archives all his repositories: "Have taken up farming"
>I love this about farmers. They are the polymaths of our age and folks dont get it.

Letting it get too complicated risks losing all of the small-scale farms because then only large companies will have the scale and aggregate skill and money to farm. Tight margins means they might decide to quit and go do something else given the amount of skill and work required for so little profit.

Being a farmer and not owning the land that you work is soul crushing.

hnthrow289570··on Software Friction
>The requirements are unclear, or a client changes what they want during development. A client changes what they want after development.

Agile supports some uncertainty, but often a mile is taken when an inch is given.

You have to take it in stride though. Developers stay employed for shipping bad or happy-path-only code all the time.

>Is friction important to individuals? Do I benefit from thinking about friction on a project, even if nobody else on my team does?

Even if you were to eliminate a lot of friction, the profit would go to the business anyway.

The military has different incentives, of course.

hnthrow289570··on The Weird Nerd comes with trade-offs
I usually see both happening at the same time, but the real money still goes to the politicians.

Brilliant nerds that solve problems for the organization on their own usually don't get rewarded as much as politicians despite the skills perhaps being more rare at the organization than politics.

For example, you could deep dive into a bug that's been hanging around, finally find the really technical solution to it, but most of the money holders won't be able to appraise that value from the technical details alone.

In general, simply giving away things to companies will usually get you taken advantage of (usually not maliciously).

Doing a tour to explain why it's a problem first, then providing the solution, is the much better alternative.

It really is true that it's a thankless job if everything is working well and you're being proactive by fixing problems before they become a problem.

There are exceptions where the money holders can deal with the technical details and don't need to be sold on the problem first, but it's rare and usually those are prestigious jobs in close proximity to lots money.

hnthrow289570··on Whiteboard interviews are a test of obedience, not intelligence
I would love a view of the code and architecture and backlog I'd actually be working on to see if it's a huge ball of mud.

I have been fooled by companies selling other perks of the company, but the actual day-to-day was terrible because of terrible code.

I've also been sold on intentions to improve the code, but which never panned out after 6 months because shipping features was still the foreseeable priority. You can sometimes find honesty up front like "we know it sucks but we're going to improve it" but that goes back to selling intentions with no real solid date for that effort. It might work out, but it's a gamble for a candidate.

Plus you also get to see incidents, how they write tickets, and sprint volatility and how much stuff gets pulled in/pushed out because priorities change rapidly (there's probably a proper PM term but I can't be arsed).

It would stop a lot of people joining, realizing it sucks, then doing their year and getting something else. Then they might actually have to improve their shit instead of burying the facts.

hnthrow289570··on Ask HN: What was your most humbling learning moment?
I'm numb to it. It's just a fact of life because tenures are so short, quality is often very opinionated, and jobs are readily available, and you usually get a raise from the next job too. You do what you can to stay employed until you can get the next job lined up.

It has become overwhelmingly obvious that the industry is never going to reach a state where technical debt and bad code is exceptional and high quality is the norm. If there is a maximum amount of pessimism I could have, it would be for this.

hnthrow289570··on Bossware is a big legal risk
We're probably at the point where it's cost effective to pay for traveling-to-interview again, especially for the later-round interviews.

That is, unless companies are lying about how much damage bad hiring does. I don't suspect they are, but they apparently can't also do the math to go back to that option.

hnthrow289570··on In software architecture you have to recognize when you're adding a rocket stage
We should definitely stop using metaphors involving things we don't understand (rocket design) to explain things we might already understand (software development).
hnthrow289570··on 'Underwater bicycle' propels swimmers forward at superhuman speed
It's pretty neat. I'd want to try a version with a linear motion that drives the propeller for the counterbalance reasons.

I could see this as an alternative to fins offered at snorkeling places. That would make a great test environment too.

hnthrow289570··on Are You an Anarchist? The Answer May Surprise You by David Graeber (2000)
>The first is that human beings are, under ordinary circumstances, about as reasonable and decent as they are allowed to be, and can organize themselves and their communities without needing to be told how.

That's a crock of shit, look at how brutal early civilizations were compared to today. You have an argument over long terms (100+ year spans), but not in the near term.

If you want the assumption to apply to the near term, you have to accept that people behave in part based on the laws and society which they grew up with, which then makes you look weird for being against that system. That's what gives rise to the common decency.

hnthrow289570··on Asynchronous Programming in C#
>You are clearly thinking about smaller projects.

Yes, because that's the majority.

You will probably not see another major upgrade from .NET to new-shiny-thing in a decade or more, so you may as well take the extra time to do things right for .NET now, even for the largest projects.

There have been multiple LTS's to target, and once you are over the initial Framework -> .NET "hurdle", upgrading from there should be much easier.

>Larger projects can't survive a "stop the world" / "go async" project.

I don't know how it would be fatal unless the company doesn't want to give you the time for it - either because it doesn't make financial sense or they haven't been convinced. .NET is certainly one of the easier languages to refactor with confidence.

If it will never make financial sense, then I guess it'll go on to join the still-running COBOL projects, but that's an outlier.

hnthrow289570··on Asynchronous Programming in C#
>MS libraries are great but all the rest seem to be enterprise-milking, poor wrappers or sdk for some cloud service.

The biggest example are PDF producing/converting libraries, which I have no doubt make millions in licensing.

hnthrow289570··on Asynchronous Programming in C#
This feels frustrating, but it is a good forcing function for the quality of C# projects.

IMO it is a great alternative to simply deprecating/breaking older things and will slowly push the ecosystem towards .NET's recent language features, which will improve readability. If a company is not putting a .NET Framework -> .NET upgrade in their near future (which is a great time to go full async), you probably don't want to be in that job for too long.

hnthrow289570··on Why We Hate Working for Big Companies (2018)
>If you're not careful, and your centralized system injects dozens of minutes of delay due to the additional complexity of performing the global optimization, you end up with the globally optimal decision from 20 minutes ago, which in the context of, say, load balancing is an eternity.

That actually doesn't seem avoidable, because some of this time will need to be spent identifying risk and malice/corruption.

hnthrow289570··on IBM to buy HashiCorp in $6.4B deal
That's alright. HashiCorp stuff was 2nd tier compared to any offerings from the cloud providers themselves just because those providers' own solutions would get preference (obviously!). And cloud is the environment for 95% of app development these days.

If HashiCorp stuff is destined to die, something else will eventually rise to fill its niche if it's still valuable.

You can always count on technology to churn for no good reason.

To avoid sounding completely pessimestic: don't discount an IBM comeback either, for the same churning reasons.

hnthrow289570··on Programming Is Mostly Thinking (2014)
Sadly like half of that wisdom has to do with avoiding personal stress caused by business processes.
hnthrow289570··on Anatomy of a credit card rewards program
>Redditors are frequently sophisticated with their spreadsheets; many of them could clearly earn three orders of magnitude more from the financial industry if they stopped thinking that the right way to monetize spreadsheet skill was in gaming credit card signup bonuses.

It's a pretty decent outlet for having something complicated to work on. Another would be EVE Online with the added bonus that it's also an actual game. My guess is most of those people are just trying to min-max what the companies allow them, rather than trying to find an exploit in the system that prints money per spreadsheet CPU cycle.

I am suspicious that anyone can get a job in finance with only churning (or EVE) spreadsheet skills. I have rarely found "well if you can do that hobbyist but seemingly proximal activity, you can walk into a decent-paying job" to be true in tech and I suspect it's true for finance too.

Maybe the finance bros just need a leetcode-for-spreadsheets website to run their technical interviews to open the floodgates though.

hnthrow289570··on What it's like to staff the home of a billionaire
Well, you need to be in proximity to wealthy people to get that information, and that's why it's under served. There's not really a public clearinghouse of unaddressed wealthy-people-problems to inform this market that I know of.
← PreviousPage 2 of 2