skysight-inc/HackerNews huggingface dataset:
I welcome the death of Framework-of-the-month and hip-language-of-the-month plague. The fragmentation is just irritating at this point and demands too much effort and time waste adapting and promoting yearly re-writing of everything because management want to cut cost and hire more cheap desperate devs.
The larger point is that by keeping non-strategic part of your tech stack boring, you can focus on core innovative technology. In this guy's case it's LLM.

Which is same point that the original post "choose boring technology" makes. I don't see the contradiction.
I really don’t understand why we give credit to this pile of wishful thinking about the AI corporation with just one visionary at the top.

First: actual visionary CEOs are a niche of a niche.
Second: that is not how most companies work. The existence of the workforce is as important as what the company produces
Third: who will buy or rent those services or products in a society where the most common economy driver (salaried work) is suddenly wiped out?

I am really bothered by these systematic thinkers whose main assumption is that the system can just be changed and morphed willy nilly as if you could completely disregard all of the societal implications.

We are surrounded by “thinkers” who are actually just glorified siloed-thinking engineers high on their own supply.
Yup. But now he gets to be first buddy.
At AWS engineering scale they can absolutely figure it out if they have the slightest interest in doing so. I've heard all the excuses — they all suck.

Businesses with lawyers and stuff can afford to negotiate with AWS etc. when things go wrong. Individuals who want to upskill on AWS to improve their job prospects have to roll the dice on AWS maybe bankrupting them. AWS actively encourages developers to put themselves in this position.

I don't know if AWS should be regulated into providing spending controls. But if they don't choose to provide spending controls of their own accord, I'll continue to call them out for being grossly irresponsible, because they are.
Well, maybe - the why of why the author thinks those technologies are best are in the catchprhrase itself (they are boring), and the motivation of why boring is good is described at https://mcfunley.com/choose-boring-technology and the like.
Because of I/O.

Without any kind of async (this includes green threads) you run out of (OS) threads very fast.

This is not a black/white decision whether Async makes sense for every API all the time or never.

It's a solution to a specific problem that occurred (and still occurs) a lot.

The article was just about the syntax though, because they are still using asynchronous programming via coroutines (or goroutines ;-))
> They can execute anything they like as root... by entering their password.

If it has control of your user account, then it can just arrange to wrap your shell prompt and wait for you to sudo something else. The sudo password prompt in its default arrangement doesn't really provide much security there and isn't expected to.
What are "T_COMMAND" and "T_STATUS"? I searched but that terminology doesn't seem to be used much
cat img > /dev/null | echo ""
Or maybe, you know, that is not true and it’s part of a character?
I am not an Apple user but I do enjoy the history of computers -- which (obviously) the timeline will reach the likes of Steve Jobs and Apple. As much as people give high praise to Steve and the rise of Apple... I personally value Steve more regarding his work on NeXT more.

To be honest, as someone who was into SGI computers as a kid, accepting the reality I would NEVER be able to own one, I hoped one day I would get to use or try one in the workplace. Of course, by then, technology had moved and these expensive machines are now affordable, simple a Windows PC with a good graphics card!

Getting back to NeXT, I heard "Next" thrown about when reading up on ID Software (Doom, Quake, etc) but never really appreciated what this was until later on. When I finally spent the time to understand that this "Next" was a computer, I started to appreciate how cool it was especially back in 1990! It made me appreciate how far ahead they were with programming/development tools. I mean.. Visual Studio finally caught up with productivity.. like.. 10 years later!

It is great to see the history of NeXT continue -- not just being "merged" into Apple but with OpenSTEP and others.

It also makes me appreciate less known programming languages that, one day, could become "mainstream" at any point. Hardly anyone knew much about Objective-C but became a popular tool for Apple developers with OSX. Thats why I always have a grin when people mock a less known language because "hardly anyone uses it" or "hardly anyone knows about it" -- that could change, you know.
Everybody Codes Challenge
For containers, you don't want EC2, you want ECS, possibly even Fargate depending on your use case. They're different compute primitives based on your needs.

There isn't a boxed product like Bigquery, but the pieces are all there - DynamoDB, Athena, Quicksight...
I think it’s nice for server stuff but on a desktop app it’s a pain to deal with. MS definitely went overboard with a lot of APIs being async only. A lot of people don’t seem to understand that async/await is still multithreading so in a desktop app they tend to mess up. Not sure how it’s in mobile.
I can't see a way to measure load average on a process by process basis as you can for % CPU.
Is it ok to do work while you're exercising? Is it ok to exercise while you're doing work?

Student of the Talmud asks the rebbe: "Rebbe, am I allowed to smoke cigarettes while I study the Talmud ?" The Rebbe categorically says "no, it would be highly offensive to smoke while studying the Talmud".
Student then asked: "Am I allowed to study the Talmud while I am smoking a cigarette?" Rebbe: "Well.."
Yes, bare metal is not a panacea. Some use cases require 0 personnel change going bare metal (even having reduced labor), and some are very much the opposite.
Show HN: Bucket – Feature flagging that's purpose-built for B2B
Howdy HN!

We're a team of 7 that have worked on Bucket for the past 2 years (Seed funded).

How are we different than other feature flagging tools?

* Purpose-built: Bucket is built for the B2B use case, which makes everything simpler for you.

* Companies over users: In B2B, you mostly target customer accounts, not individual users.

* Quality and craft: We're sweating the details so you can focus on releasing better features.

* Product engineering: We've made it easy to get feedback and adoption metrics on new releases.

* Entitlements: Easily manage feature access based on customer SaaS subscription.

Would love to get your feedback on the product!
Have you tried voicing it out loud and recording yourself?
Earlier this year. I did have pretty bad luck, then did some contracting, then converted that into an FTE role.
I would encourage you to check out the "No Free Lunch" paper[1]. tl;dr the correct approach depends on the problem, there is no approach that is superior to all others. There are a provably infinite number of optimization problems where RANDOM GUESSING is superior to any other algorithm.

(Note: I am not claiming support for the methodology in the paper, I just find the application of search/optimization algos is lovely)

That being said back before I understood how to program gradient descent I would often use Evolutionary Algorithms such as simulated annealing to optimize NNs! (never claimed it was state of the art, I just wanted to build and optimize some small networks by hand and my calculus was pretty weak at the time)

[1]: https://en.m.wikipedia.org/wiki/No_free_lunch_in_search_and_...
Shoutout to h0ffman, in my opinion the best contemporary junglist on olschool hardware. His 8-Bit Jungle music disk: https://www.youtube.com/watch?v=--J66FY7qro
> It's not ossified but efficient.

These are just assertions. Efficient compared to what?

> If a company like Google with about ~180.000 employees

Why should an organization even have 180000 employees? What determines the distribution of size of organizational units observed in an economy?

And given an organization's size, what determines the height of its "pyramid"?

The fact that management consultancies are making (in perpetuity) a plush living by helping reduce "middle management layers" tells you explicitly that the beast has a life of its own.

Empire building and vicious internal politics that are disconnected from any sense of "efficiency" are pretty much part of "professional bureaucracies" - just as they are of the public sector ones. And whether we are clients, users or citizens we pay the price.
Thanks for your response--that's incredible stamina to do that for 3 months.
https://archive.is/bDczv
RSA is hard to secure? As far as I know, 2048 bit RSA has still not been cracked?
The worst thing to happen to programming you say?

Worse than null-terminated strings in C? Worse than null being return on failure of dynamic memory allocation? Worse than nullability of columns in sql which Tony Hoare (the author) called "my Billion-dollar mistake"? Worse than the Knight Capital update bug that caused a $440million loss in 45minutes meaning Knight went out of business and was taken over? Worse than the innovative design of Therac-25 that caused deaths and serious injuries by giving patients 100x the intended doses of radiation? Worse than the Fujitsu Horizon system that lead to deaths due to stress and suicide, innocent people being put in jail etc...?

I could go on but you get my point.

What a staggeringly stupid headline in service of clickbait.
Could be, but he does not strike as someone who is looking for fame.
Plus the whole discussion about why he would like to move to SF but can't seems pretty authentic.
For AWS the solution for container deployments (without dealing with VMs) is Fargate, which imo works reasonably well.
What about the billing dashboard? You can break it down by service and say CPU or memory, or tags if you use them. That has always given me good enough insight into where my client's money is being spent. I'm not sure it's totally realtime, but certainly daily.

BTW I'm a supporter of spending caps, not saying this should be the only way.
Yes it is not ethical to check for updates if the user didn't agree for that.
I’ve emailed security and they said they would contact the cloud-init folks.
The IC ladder at Google grows from L3 up to L10.

An L8 IC has similar responsibilities as a Director (roughly 100ish people) but rather than people, and priority responsibility it is systems, architecture, reliability responsibility.
Yes, every data point is worth taking a look at and considering. That's not the same as agreeing. And yes, there's a long history of Russophobia - especially in Western Europe that goes back to "uncivilized hordes from the east", to the Great Game competition (why the British in particular are so vapidly anti-Russian), then the more recent anti-soviet/communist mentality (excluding the current modern Putin era).
Someone probably said the exact same thing when the first cars appeared.

Where is the data showing that more jobs get destroyed than created by technological disruption?
It became crystal clear that cups is a can of worms, and it would be prudent to completely replace it with with a new solution built from the ground up, ideally using modern tools and standards.
Ultrasonic stir welding is already a thing: https://technology.nasa.gov/patent/TOP8-95
My beef is with Web Crypto. Why are encrypt and decrypt async?
I think that anybody who finds the process of clumsily describing the above examples to an LLM in some text box using english and waiting for it to spit out some code which you hope is suitable for your given programming context and codebase more efficient than just expressing the logic directly in your programming language in an efficient editor, probably suffers from multiple weaknesses:

- Poor editor / editing setup

- Poor programming language and knowledge thereof

- Poor APIs and/or knowledge thereof

Mankind has worked for decades to develop elegant and succinct programming languages within which to express problems and solutions, and compilers with deterministic behaviour to "do the work for us".

I am surprised that so many people in the software engineering field are prepared to just throw all of this away (never mind develop it further) in exchange for using a poor "programming language" (say, english) to express problems clumsily in a roudabout way, and then throw away the "source code" (the LLM prompt) entirely such to simply paste the "compiler output" (code the LLM spewed out which may or may not be suitable or correct) into some heterogenous mess of multiple different LLM outputs pasted together in a codebase held together by nothing more than the law of averages, and hope.

Then there's the fun fact that every single LLM prompt interaction consumes a ridiculous amount of energy - I heard figures such as the total amount required to recharge a smartphone battery - in an era where mankind is racing towards an energy cliff. Vast, remote data centres filled with GPUs spewing tonnes of CO₂ and massive amounts of heat to power your "programming experience".

In my opinion, LLMs are a momentous achievement with some very interesting use-cases, but they are just about the most ass-backwards and illogical way of advancing the field of programming possible.
Money in their pockets as quick as possible and no take backsies.
They want people to be passionate about whatever but in my experience the younger guys/gals are so preoccupied with themselves or some process that they spend endless hours discussing it instead of just getting some shit done.
question still remains - how did it get there? Never had any interest in the daily builds
> This was not why freedom of the press was granted

Not about this specific point but people making these decisions back in the 1700s and 1800s were at least as flawed as us (arguably much more) and made some extremely horrible/stupid choices in hindsight.

Treating them as effectively infallible religious figures is well.. just that.

Especially if we consider that the interpretation of what freedom of speech (and press) meant was extremely narrow by modern standards well into the late 1800s and beyond.
If you don't know how to use a knife you will get cut!
Because otherwise the main thread will be blocked while those operations take place and the whole ui will freeze
I personally can't relate, but that's because I've never been in any organization at that scale, biggest companies I've been had employees numbering in the thousands, of which IT was only hundreds at most. There you go as far as having scrum teams with developers, alongside that one or more architect, and "above" that a CTO. Conversely, companies like Google have tens of thousands of people in IT alone.

But likewise, since we're fans of equality in my country, there's no emphasis on career ladders / progression; you're a developer, maybe a lead developer or architect, and then you get to management, with the only distinguishing factor being your years of experience, length of your CV, and pay grade. Pay grade is "simply" bumped up every year based on performance of both you personally and the company as a whole.

But that's n=1 experience, our own company is moving towards a career ladder system now as well. Not nearly as extensive as the big companies' though.
As always, it depends on what style you're talking about. For mainstream EDM? Sure I won't fight your figure. But for underground techno (among many others), you're delusional if you think the majority of djs play pre-recorded mixes.
L5 isn't the highest IC level at Google. Broadly would go up to L10, but the ratio at every level is ~1:4 or 1:5 b/w IC levels.

The L7/L8 level engineers I've spoken or worked with have definitely earned it - they bring to bear significant large scale systems knowledge and bring it to bear on very large problem statements. Impact would be felt on billion$ impact wise.
I think Medium is worse
Ah true! I fixated on exactly the line that was marked. I guess it's not that bad because you're choosing the file to copy, but I wouldn't have used a subshell for copying a file anyway.
It is quite annoying for older codebases in C# that have a lot of existing sync code, but for new code it doesn't matter all that much. You use async methods for IO and DB access and in many applications this means that most of the methods will be async.

I only played around with it a bit a long time ago, but I didn't find Go concurrency as simple and easy as it is often sold. It felt very low level, which is fine for the design goals of Go, but also meant that I was still left with doing some harder parts myself.

Concurrency in C# with async/await is pretty easy for the straightfoward cases that make up most of a typical application. You do have to keep to a few rules and it certainly has very dangerous footguns, but those are minimized if you use consistently use async methods instead of sync.
You can want whatever you want, including a new metric that measures and portrays things however you wish.

The existing metric is not what you want. And that's perfectly OK: There's absolutely no damned reason why there can only be one. This isn't Highlander.

Edit: Lol, the King of Egypt rang and basically said this while we were chatting. Also [additional appeal to authority] and [someone's mom].
well others seems to be getting the meaning (whether they agree or not is another matter), so you might be too habituated to the "L" world to bother understanding?

> if this comment weren't so short i'd swear it was written by chatgpt.

ditto
> Japanese brands long have and continue to absolutely dominate long term reliability ratings for vehicles

such hard earned experience is no longer relevant in the era of EV.

> but the European Volkswagen and BMW Groups are still competitive

none of them is even capably of designing self driven cars on their own. same for the AI based infotainment systems fitted on EVs. they are just Canon in 2024/2025.

> EVs are still a luxury good

I wouldn't call it luxury. It is the cheapest option to own a car in Shanghai, BYD Seagull is being offered for $9k USD.

> Japanese brands are primarily mainstream

they have already lost the battle. if EV makers can't build their own self driving systems and those AI based infotainment systems, then they are in the wrong business. Batteries is another story that can not be ignored, Japan and the EU do not have any meaningful control on that.

I don't see any chance how European or Japanese car makers can survive in mid term.
All sorts of problems there. It means that you can't spin up a stack for an hour if the system calculates that leaving it online for a whole month would breach your limit. If the original author had a $100/month limit he wouldn't have been able to spin up the stack even once.

Also you have variable costs (like s3 traffic) that could put you over your limit half way through the month. Then how does AWS stop you breaching your limit?

On a more practical level I don't think AWS keeps tracks of bills on a minute-by-minute basis.
First time I've used S3 glacier in a wrong way and downloading few gigabytes resulted in multi-hundred dollars bill. I don't remember all the details, but it was absolutely non-obvious behaviour. I think it was corrected since then and today it wouldn't work like that.

Second time I've configured virtual machine with some fancy disk. It was supposed to work as CI build server, so I've chosen the fastest disk. Apparently this fastest disk was billed by IOPS or something like that, so it ate few thousands of dollars in a month. I couldn't even imagine disk could cost that much.

Basically these pricing nuances contradicted everything I ever encountered on multiple hosters I worked with and it felt like malicious traps designed specifically for people to fall into.
You'll find this convention in other JS crypto stuff as well, like libraries for password hashing. Eg:

https://www.npmjs.com/package/@node-rs/argon2

https://www.npmjs.com/package/bcrypt

Though the bcrypt package does provide an additional sync API. (You should be using argon2 though.)
I love async and await its one of the best things to happen in programming.

Simple solution to concurrency.

I appreciate its hard to grasp at first but it’s literally second nature now I rarely need to even give it much thought.
I clicked and see the operating system screen, but how can I use a console?, there are only ads at the sides.
so in two words: Champagne socialists
The older the tech, the more training data should be available for it (assuming it's still being used today), ergo LLMs will be a lot better at it. They ought to be way better at Cpp or JS than Golang in that sense.
I think the article confuses "spinlock" with "busy-wait", which made me confused too.
I second your view. Either i work, or i do something else.
Often when i read about people's ideas, like this article, it helps confirming "being on weirdo level" is truly something else.

Next: shitting while cycling and working?
Yes? To an almost extreme degree?

I don’t recall Zuckerberg ever buying himself a cabinet position. Do you?
Cause they can be slow.
The only original insight of this blog post is that it's nice to be able to use `sleep()` without async/await in Go, which is also true for Rust and Rust has Async.

It does not stem from async/await that Javascript doesn't have sleep()
Or anything for corporate use where the customer is a beancounter and the user is an employee, stereotypically.

Or education, where it's possibly a politician or a government beancounter and a student.
Great to finally get a solution for B2B feature flagging instead of building a custom solution that we have to maintain.
As someone who was so non-conformist in the 90s that he refused to listen to the music for non-conformists, I am constantly surprised that jungle doesn't sound the way it's named. Every time I expect EDM with Afro-Caribbean percussion, like bongos and steelpans and marimbas, realize it's nothing like that and promptly forget what jungle sounds like until the next revelation.
If only.....the banks believe it's a better investment to destroy the planet. Let's not even mention the hubris of tech companies.
Over the store or how?
Yes, but you can offer both sync and async methods. Web Crypto only has async.
Ha, I have to agree with you. Fluff all the way down.
I have worked both in the EU and in Brazil and I do have to say that the Brazilian system is better. Labor protection is high (25 vacation days, guaranteed overtime pay, etc), but companies can still fire people. However doing so involves paying severance proportional to how long you been at the company.

When you leave a company you need to give one month notice (so you can't just get up and leave). I never seen a "layoff" (you get notice that you are leaving, but still have your job for a few months and usually no severance) like they do in the EU. When you are fired, you are out of there the same day with your severance and unemployment benefits.

This specific practice does have a few problems:

1) companies not firing about-to-retire employees who have been at the company for 10+ years because of the huge severance required. Instead they just wait for them to retire. However employees also really don't want to get fired in their last few years either before retirement because of how the pension system works, so it balances-out. 60+ year old people usually take it easy, but they are usually not just showing up for a paycheck.

2) Younger employees trying to get fired instead of quitting. If you been at a company for 3-4 years and you want to leave it is really a lot more beneficial to get fired instead. I have seen this happen, but not nearly as much as you would think (at least in IT).

Although you would think companies would want to "recycle" employees by firing them every year to prevent the severance from piling up. The math doesn't really work out like that on top of all possible disruptions of such high attrition rate.