Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The bottleneck was never the code

thetypicalset.com

Post reply on HN
Print view View original

441–446 of 446 posts

Re: The bottleneck was never the code

#441

Post by alternatex »

empthought wrote: post #305
alternatex wrote: post #194

Earlier quoted context omitted.

Bottom line is the people described as hypocritical in the comment have no principles, but rather feign passion in anything they think other people consider valuable. When devs thought coding skill was valuable, that's what they claimed to be passionate about, when the game changed and communication became key, they suddenly changed their passion. Either the timing is a coincidence, or they are hypocrites. I don't th…

You're trying to turn flexibility and the ability to adapt to new circumstances into a vice. You're wrong. It's a virtue.

Adaptability is a virtue, flip flopping is being disingenuous.

Re: The bottleneck was never the code

#442

Post by robertlagrant »

moralestapia wrote: post #282
goatlover wrote: post #267

Earlier quoted context omitted.

Because a claim was made about a group of people.

Exactly. Does it matter if one member of that class does not follow the trend?

My point being that it's unlikely that it's that way round. It's more likely that there's no actual trend, and there are one or two that have done it and they've just extrapolated.

Re: The bottleneck was never the code

#443

Post by sevenseacat »

skydhash wrote: post #159
neogodless wrote: post #130

Earlier quoted context omitted.

For business, software applications are tools that facilitate "the thing" that generates money. (We in the software world think that _thing_ is software and software _features_, but outside that world, there's usually a different _thing_.) The bottleneck for making software applications better at being used by (non-software) businesses is making sure the software does all the software things that actually benefit the…

> But yes, the speed can really help. You can prototype and trial and improve the feedback loop. Based on what I’ve seen, prototyping has been always easy. You don’t even have to build software for the first iteration. For UI stuff you can use a wire-framing tool. What has happened is that we abandoned the faster iteration methods (design think tank, quick demo and UX research,…) and we have full in on building the f…

Dealing with this exact issue now. 'Design' has become a dirty word to some folks - so much so that they've come up with new 'ideas' like 'simulations' to get feedback from users...

Re: The bottleneck was never the code

#444

Post by sevenseacat »

HarHarVeryFunny wrote: post #121

> What may save us it that agents are unreasonably good at reading exhaustively. An agent will read every PR comment, every closed issue, every commit message, every stale design doc ... > Not just “this module exists,” but “this module is weird because the migration had to preserve old behavior,” or “this benchmark matters because a previous optimization silently changed the distribution.” The thesis here is that an…

Whenever I see comments more than a few lines long in an AI-generated PR, that's a pretty good indicator to me that I should pay extra attention to this part because its most likely incorrect. A lot of invalid assumptions, wrong inferences about behaviour, incorrect descriptions of behaviour, and so on.

Re: The bottleneck was never the code

#445

Post by abduhl »

roenxi wrote: post #432
abduhl wrote: post #171

Earlier quoted context omitted.

This is shifting the principle/value discussion up to a level where it's meaningless. Let's use a different example. Old value: Returning value to shareholders. How to do it? Treat your employees like family and don't be evil. New value: Returning value to shareholders. How to do it? Treat your employees like human resources and get away with what you can get away with. Is this hypocritical? Most people would say yes…

> Is this hypocritical? Most people would say yes, but in your framing it's not because we've backed up to the least specific articulation of an underlying principle. It's a species of the motte and bailey fallacy. I'm happy to defend that one too, for the reasons you outline. It is completely normal behaviour from a company, everyone understands it [0] and most managers I've worked with would be happy to talk about…

I think our disagreement is with respect to what it means to "claim" to be following a principle. Most people do not say "my principle is X," they just make statements that hint at a core principle. In many cases this is willful, as you aptly point out for corporations, and it is specifically for the reason you are articulating now: if you never state a core principle you can always back into one later that is not hypocritical. I reject your framework where a principle must be explicitly articulated and cannot be inferred by statements/actions.

Re: The bottleneck was never the code

#446

Post by biggoodwolf »

martin- wrote: post #389
moralestapia wrote: post #282

Earlier quoted context omitted.

Exactly. Does it matter if one member of that class does not follow the trend?

No, but no-one said that. It's far more likely that this "group" of people doesn't even exist, and it's yet another case of treating "strangers on the internet" or "other people" as one person and being upset when that "person" is being inconsistent.

Groups exist
Post reply on HN