solididiot

Worked for a much lesser international company and it was exactly the same minus the politeness. I had to find a quiet corner to get some work done.

<cynic>Yeah React is already so last year.</cynic>

Only read the transcript but I'm not getting most of it. I mean it starts with a bunch of aphorisms we all agree with but when it should be getting more concrete it goes on with statements that are kind of vague.

E.g. what exactly does it mean to: >> Don’t use an object to handle information. That’s not what objects were meant for. We need to create generic constructs that manipulate information. You build them once and reuse them. Objects raise complexity in that area.

What kind of generic constructs?

How do I know whether this thing isn't already here "commending" in this very thread?

I wouldn't be so sure. Programmers (and drivers and cashiers) can "survive" in poverty like millions others already do. This transformation is coming in waves that keep the proverbial frog in the pan.

Does it need to solve original problems? Most of the code we write is dealing with the same problems in a slightly different context each time.

As others say in commends it might be the case where we meet in the middle. Us writing some form of tests for AI-produced code to pass.

> There’ll be several new career paths made possible by this technology as greater worker productivity makes possible greater specialization.

Can you list a few?

The same Ginni who walked away with a huge bonus?

I think this is the new normal. Either open/close as soon as a more dangerous variant comes along (can happen with most of the Earth population unvaccinated). Or just let it be and get used to health system being on its knees on peak seasons and more vulnerable/unvaccinated dying of.

If it where sterile then we wouldn't test it in medical tests.

> Keeping an eye on the weather, studying charts carefully, picking good anchorages, and having a good rode and anchor was our best possible insurance, but there are dangers that are beyond anyone's control, dangers that even the most skilled sailor cannot avoid, e.g., a shipping container adrift, dead heads at night, whales, etc.

dead heads at night. What is that?

Yeah we only do that metaphorically in the modern world.

Couldn't agree more. I was working in a company that didn't allow local checkouts. You'd have to work in a remote VM. Next step was going to fully remote desktops (i.e. dumb terminals). For security reasons (whatever). I hated every moment of it as it made feedback times longer and for doing anything at all you needed to beg the IT people. But the weirdest part is that other devs didn't seem to mind. (Not to mention all the spyware crap installed on our machines and the whole mentality of security over productivity. All of it -security- sold to us by third parties as a service (nvm how absurd it is to trust N other companies to keep you secure). Anyhow this place was surreal but I'm afraid it's not the only one).

So to answer the question of how we came here: The same way anything in the commons sphere rots and dies. Not enough people care enough about it. They're OK giving away control one way or another and companies are more than happy to sell it as a service. What user gets in return is diminishing but once the process starts it's kind of runaway I'm afraid.

It's fascinating how much the ageing West is fascinated by feats accomplished by as young as possible people.

All good points. Thanks

More like "throwing the towel" than "accepting"...

What kind of blog is that?

I mean if you navigate to the index https://joearms.github.io/index.html#Index it says that this is actually a Quine.

There's something much worse than Leetcode. Take home unpaid long projects that end up in rejection or lowball offers.

Regardless of the specifics here, I'm pleased and envious of being reminded that some people have meaningful jobs that actually make a difference.

thanks for sharing that

Heavily off-topic but I think he means that you pay and get the test _before_ actually making the trip on which you might actually get the virus. Which indeed makes no sense other than making Dublin airport richer. OTOH if you spend some time in Dublin I'm afraid you get used to burning money for no good reason as the city has become absurdly expensive in recent years.

SOLID and a dozen of DPs and you get there pretty fast. Then you rewrite by another team with their interpretation of SOLID and another dozen of "better suited" DPs and you get there again. On 3rd iteration you just buy something as a service that covers 80% of your needs and consider the rest 20% non-essential business. And life is finally good.

Interviewing has become a theater of the absurd.

You get examined on things that won't be useful in 99% of your work.

People put in hours to prepare and game it.

Overall countless hours go to waste to just play the role.

Most times it doesn't even show whether someone can think (what you might see as thinking might be well rehearsed "act as dumbfounded for a while").

I wonder if there's a jobs dir for non-profits etc.

My job pays enough

What if that wasn't the case or you were unable to find a job altogether? Would you still think the exact same way?

So, unicorns in 2022 seem to do support by Hacker News pledge.

Good luck resolving this.

That and a career train-wreck.

Is there before?

1. You manager is managing you to the benefit of himself and the company. Not yours... You are being played. The larger the corporation the harder you are being played.

2. You won't make any friends at work and after you leave it nobody will care.

3. When there's packages on the table take yours and get the hell out of the quagmire you work. You will find another job. (See 1 again).

4. Take deep breaths when you start feeling angry.

5. Don't work with teams where no-one ever reads any book.

6. Don't work with teams where they're holding one or more books as Gospels.

7. Do not work for arseholes. Unfortunately you'll usually know they're such after you spent some time working for them.

8. Do not kill yourself working so that somebody else can cash out big. Do not even sweat for such a cause.

9. Do not buy in mission-statements and culture. There's only one mission. To make profit. Prefer to work for someone that admits it.

I'd personally not work on SW that could be used by someone else commercially at zero expense. In that sense I never understood why people moved away from GPL and started using "do whatever you want"-license types.

Funny trivia. I spent considerable time working on corporate SW that acted as a gatekeeper for GPL-like licenses. It seems that one of the worst things a corporation can do to itself is use free SW with such a license. Nope. And why should they? There are so many options with so-called "friendly" licenses. Friendly to the corporation that is.

I see it as another aspect of huge corps evading any kind of taxes and IT-crowd actually being OK with it. I mean an unknown dev would be more than proud to do free work for K8S (and many do) just for the sake of putting it in her CV and _maybe_ cash out on it with a better paying role later on. But the fact remains. She, essentially, worked for free for Google, Amazon, Red Hat, etc. All the same as she is OK(ish) with them tax evading because if you get to work for them you'll be extra rewarded (unless you disagree that much of the huge salaries in IT are down to tax evasion).

In any case if you approach FOSS romantically I think you're in for a big let down. It's some form of business transaction. Nebulous and tricky but business nontheless.