what was particularly interesting about that experiment was the fact that you could pack quite a few images in a very small network.

They are not. The only reason one might think the solution is novel is because they never saw it before, but what they are actually receiving is an excerpt from someone elses blog post or stack overflow answer. [1]

A bit terrifying thought experiment is to accept for a moment that programming is dead and all its left prompt engineering. Fast forward 5-10-15 years and whos left to actually produce new code and ideas to feed LLMs?

[1] one thing I like to do from time to time - especially when I'm asking for something I know little about - is to copy and paste the answer back to google and look where did that answer originated from.

One time I asked a very specific linux shell command and the answer didn't sit right with me. I googled it and it pointed me to a stackoverflow question. It was the first answer with ~1000 upvotes. But it also had a comment with ~700 upvotes explaining why you never ever should do that. :)

My mental model and go to ELI5 is "imagine you compressed the whole internet into a zip-like archive and you have an extremely clever and efficient way to search it for data".

I'm old enough to remember the time when you could order wikipedia on CDs and I don't see much difference between that and downloading LLM.

I still believe it's a good piece on your powerpoint if you want to teach. It's easy to fall, easy to grasp, and easy to unroll all the rules - that is, if the rules are actually set in stone.

On the other hand I've been through couple FAANG interviews, and twice I was presented with something similar and after I glanced at it for a half a minute the interviewer quickly proceed to "a ha!, you don't know! the interview is over , but I'm happy to tell you the right answer".

That part is not cool.

I literally went to an Apple Store the other day after every influencer released their video on yt claiming that it's a great computer, you just have to install the pad in less than 3 minutes and it will work like a charm...

So I asked the salesperson about that and they told I'm not allowed to tamper with the device and it will void the warranty.

Source: apple store staff

Seasoned, well trained engineers have created hundreds of thousands in billing on AWS through a simple mistakes overnight.

It's immediately reminds me of putting microtransactions into children games on mobile devices - a venue that has been thoroughly explored some 10-15 years ago.

I can't see payment and provisioning as a blocker in any scenario.

This has a potential to create a massive yet very dubious income stream for the company.

There are many people who would consciously love to stop drinking but can't find alternative to stop the storm in their heads. This could be caused by many things, from trauma to ADHD.

The best quote I heard about addiction is: "I only have control over my first drink".

The worst part is that alcohol and drugs have a strong stigma, but for people who are suffering anything that can turn their mind off is viable, gambling, binge watching tv or playing video games. The latter are often overlooked and ignored by relatives.

The issue is almost always feature management.

Back in the days I was making Flash games, usually a 3-5 weeks job, with no real QA, and the project was live for 3-5 months. Every time I was ahead of schedule someone came with a brilliant idea to test few odd things and add couple new features that was not discussed prior. Sometimes literally hours before the launch.

Every time I was making the argument that adding one new feature will create two bugs. And almost always I was right about it.

Fast forward and I'm working for BigCo. Few gigs back I was working for a major bank which employed supper efficient and accountable workflow - every release has to be comprised of business specific commits, and commits that are not backed by explicit tickets are not permitted.

This resulted in team having to literally cheat and lie to smuggle refactors and optimizations.

Add to that that most enterprise projects start not because the requirements were gathered but because the budget was secured and you have a recipe for disaster.

I strongly disagree, but it made me chuckle a bit, thinking about labeling software as "handmade" or marketing software house as "artisanal".

Let say I am a junior SWE in EU. I incorporate in Estonia and issue my employer with an invoice from said company. That company pays for my house, my car, my dental service and whatnot, and what's left I take as a employee salary.

I pay local tax for that salary, but that's only a fraction of what I've billed my employer.

It is only when he decides to withdraw the money the problem occurs.

What you're saying applies to most EU countries. Here where I live you have to reside for majority of the year in given residency to pay taxes over there.

Here's the tricky part.

Estonia is part of Schengen Area. Which means you can travel there and back without passport. There's no paper trail of your arrangements. You can easily create a reality in which you reside there for majority of time.

But again, that's not the selling part of Estonian LTD. Which is - it's extremely easygoing and as long as money stays in the company you're not paying taxes.

When Adobe suite was de facto standard for designing and coding interfaces (you know, Flash) their own software was so immensely bad that there was enough material for a guy to make fun of them on a daily basis for a good couple of years.

It is customary to announce the fact so that the astrologers can proclaim that the population of recruiters on linkedin has increased.