Hacker Newsnew | past | comments | ask | show | jobs | submit | padjo's commentslogin

> That money could go to... I don't know... feed people? Just one example.

Or even keep it in NASA and do something where we actually learn something new. It's crazy to me that we've still only sent one craft to Neptune and it was nearly 40 years ago.


Also: stop installing random extensions

A lot of extensions on LinkedIn are necessary because of their total lack of innovation. You really cannot do anything in B2B sales or recruiting with only LinkedIn tools. These are not random extensions, but crucial extensions literally saving billions of dollars in wasted time or creating massive opportunities in the global economy.


It feels like they launched actions and it quickly turned out to be an operations and availability nightmare. Since then, they've been firefighting and now the problems have spread to previously stable things like issues and PRs

They rushed to launch Actions because GitLab launched them before.

BTW, GitLab called it "CI/CD" just as a navigation section on their dashboard, and that name spread outside as well, despite being weird. Weird names are easier to remember and associate with specific meaning, instead of generic characterless "Actions".


We added Actions for CI in 2020. A year later realized our entire deploy pipeline just assumed it would be up.

Webhook doesn't fire, nothing errors out, and you find out when someone asks why staging hasn't moved in two days.


MS burning trust with people to do some stupid marketing is on the fewer assumptions side of Occam's razor.

Yeah there's no way a fax actually gets printed for this. I worked in an admin role like this 25 years ago and incoming faxes went straight to PDF on a network share even back then.

At least one of them is sitting on a raspberry pi in my house. Rather than pay a subscription for a workout tracker app or learn and configure a bloated open source one, I built my own in a few hours with Claude with the exact feature set I want. Its been a joy to use.

They certainly behave as if they do.

A third argument is that it was because of aliens from the planet Blotrox Prime. But I suppose without evidence we'll just have to accept that all three theories are equally probable.


Interesting how you decided to switch to hyperbole instead of providing evidence for your claim. Backing up your viewpoint would have easily shut me down, putting the ball in my court to do the same. Instead you gave a knee-jerk childish response.


Interesting that rather than try to bolster your claim you resorted to a logical fallacy to justify it.


Hypocritical; you did the same with the hyperbole. Why are you stooping to my level instead of being the better person?


Nope. Just a reductio as absurdum that you decided to counter by asking that I maintain higher standards of debate than you.

The notion that atomic architecture came about because people are stupid and performative is not really useful. Its fairly misanthropic and begs the question why it became so prevalent in JS specifically.


The philosophy was kinda refreshing in the early days. There was a really low barrier to publishing and people were encouraged to build and share tools rather than hoard things. It was probably somewhat responsible for the success of npm and the node ecosystem, especially given the paltry standard lib.

Of course, like most things, when taken to an extreme it becomes absurd and you end up with isOdd.


I think the issue is that the JavaScript ecosystem is so large that even the strangest extremes manage to survive. Even if they resonate with just 0.1% of developers, that’s still a lot of developers.

The added problem with the atomic approach is that it makes it very easy for these fringes to spread throughout the ecosystem. Mostly through carelessness, and transitive dependencies.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: