islon

But that's not a problem. These companies pay so much that they have too many candidates applying all the time, so missing good engineers is not a problem, but filtering out false positives is.

Though, I don't agree leetcode is a good interview practice.

That's the thing I like about HN: you can find comments that are much better and more insightful then the article itself.

As an old time gamer I can't agree more. We are in the golden age of old-style games (hollow knight, disco elysium, stardew valley, etc). People are making this old style games with all the hindsight of modernized mechanics, better control schemes, more accessibility, stylized graphics, PC releases.

Here in Cologne I see most people paying with debit cards, with the exception of very old people.

> For example I can't draw faces but I can recognize a badly drawn face. If I ask an AI: Please draw me a 35 year old man with receding hair and crooked teeth I can quickly validate the result is fit for purpose.

But code is not a face: you can't easily judge if it's correct or not, if you could you wouldn't need copilot in the first place, so now you have to trust it's correct and, if it isn't, you need to search for the correct answer anyway.

Devs complaining that the JVM is too heavyweight for client applications when electron is dominating the desktop landscape.

Satire is dead...

Jira and confluence resource hogging is such a low hanging fruit it may as well be laying on the ground for someone to pick.

Confluence search for me is one of the worst offenders: takes forever to load and can't find anything I want. Confluence is where data goes to die.

Agree, but you are giving a more extreme example.

Most rewrites I saw was "wow, this Java code from the old team is a mess, let's rewrite it and, in a couple years, the new devs will think the same about our rewrite."

They already decide to keep Kotick... not a very good start.

But old games were not pixelated. The low resolution tied with the blurry, leaky old CRTs made sure of that.

The problem is our monitors, nowadays, are too good so we see pixels that we never saw back then.

Isn't this the plot of The Last of Us?

I have an open source project in which I work alone.

I never work directly on master, always on a branch, and when I'm done I create a PR for myself.

Can't remember a single PR that I reviewed where I didn't find some issue or bug.

I guess you can say I don't trust myself...

Non native speaker here. I always pronounced the b in debt and in doubt.

Learned something new today =)

Are they releasing processors with typed registers now?

AFAIK registers and assembly is untyped.

Democratization of code will be the same as the democratization of medicine: anyone can go to a pharmacy and buy aspirin, ibuprofen, vitamins, etc. That doesn't mean physicians are jobless. Also if you have some serious problem or disease you shouldn't self medicate, but get professional treatment.

If we could create a editor so good that it can generate all you app in a couple minutes, it means the "editor" is a strong AI that can take vague, subjective descriptions an generate a working, correct program (like a programmer would do). If that's the case you don't need programmers anymore: just put the customer in front of the AI and let them design the software.

But them if you have such AI, every job would be obsolete.

Denuvo is easily cracked for games people care about. It's not put in games to stop crackers, it's put there to allow the game to go through the first weeks (where 90% of the sales happen) without competition from pirated versions.

After this time some companies even remove the DRM because it already did it's job.

The whole game industry is based on hype in the hope people buy on day 1 or, even better, pre-oder the games. One reason most big games are released broken or in a very buggy state.

Nah... it's much worse: you're buying a banner that hangs over your head saying "I own gucci clothes", but you're still naked.

Sure, because facebook, goggle, twitter, etc. are all run by the almighty algorithm and not by the crooks behind it who made it to do exactly what they expect.

Meanwhile the two interns just finished the same web app using php, mysql and jquery because they didn't know any better.

I think it'll be much more likely that the AI writes the tests (the boring stuff) for the buggy code I write.

A coaster that allows you to play Doom.

This post reminds me of what happened some weeks ago at my job.

We use Clojure and yesql (a library where you write sql queries directly in .sql files and the library generates functions for you). The devops noticed one of our queries was slow and taking too much DB resources. He sent us the query which we promptly found and then asked us if we could change it to a more performant version he just wrote.

We took his query, just replaced in our sql file and deployed. 10 minutes later he came back saying things look much better and the query update really helped.

I wonder how much time it would take if we were using JPA/Hibernate as we used to, many years ago.

Most people don't need a vaccine for that...

Why would map have conditions?

    //pseudocode
    map(f, ns)
      for i in (0 .. ns.length - 1)
        f(ns[i])

Hopefully it's not alien: isolation or dead space, or he may have trouble sleeping at night.

> reasoning about null is trivial in comparison

So trivial that its creator called it the "billion dollar mistake" and if I had $1 for every NPE I saw in production I'd be a rich man.

Cristoph is german. Meaning Kate already started drinking four years ago :)

It's such a "massive" problem I've been doing CLojure full time for the past 8 years and only heard about it now.

Every time I read about such things I imagine what kind of things are we doing now that people 50-100 years from now will comment and laugh about.

It is difficult to get a man to keep his moral compass, when his salary depends upon his not keeping it