000ooo000

Let's see throwaway1492's code

What this delusion seems to turn a blind eye to is that a good chunk of the population is already in those roles; what happens when the supply of those roles far exceeds the demand, in a relatively short time? Carpenters suddenly abundant, carpenter wages drop, carpenters struggling to live, carpenters forced to tighten spending, carpenters decide children aren't affordable.. now extrapolate that across all of the impacted roles and industries. No doubt someone is already typing "carpenters can retrain too!" OK, so they're back to entry level wages (if anything) for 5+ years? Same story. And retrain to what?

At some point an equilibrium will be reached but there is no guarantee it will be a healthy situation or a smooth ride. This optimism about AI and the rosy world that is just around the corner is incredibly naive.

Came here to say this.

>What We're Losing

>1987-2024: X11 Evolution

>37 years of continuous development, bug fixes, and feature additions. Stable, predictable, and extensively documented. The XLibre project continues this legacy with active community development.

This is a very charitable interpretation of the situation, and to suggest XLibre, which got forked 2 months ago, is the future is insane. Would be a different story if XLibre had been around a few years but 2 months is very young..

To speculate, a lot of devs seem to have a 'not GitHub? Ew..' attitude. Having used the top 4 forges professionally (BB, GL, GH, AZD) I am the opposite, so I run Forgejo at home. I don't have public projects though.

Savvy management know how to insulate themselves from such accountability. I've never seen anyone held accountable for large-scale f-ups.

You have it backwards

*Optimising My Claude Usage Around Their Usage Limits

Your sleep regime here is in no way optimal

100%. I don't trust AI to give me accurate info, even when I can clarify and fact check it at the time. This is just secondhand slop.

You only have to look at the C# GitHub repos where MS enabled Copilot, and the utter ridiculousness of those interactions between the likes of Stephen Toub and the bot. It's comical.

Stop with this infantilising crap. People can have both rewarding relationships and pastimes. Just because someone likes configuring software does not suggest they neglect their relationships or have delusions that need correction about the value of things in their life.

You're still arguing from the point of view of someone who doesn't want to do it or isn't interested in doing it. Your GP said you 'get' homelabs but it's increasingly clear you do not - and that's ok. People run homelabs because they enjoy learning and tinkering. If they don't enjoy it, or they can't risk having the odd problem, they have other options they can explore. It's not really any more complicated than that. Believe it or not, people are capable of evaluating the tradeoffs and making a sensible decision about what to host themselves.

Pretty long article with not a great deal of substance beyond what is mentioned early on. Would be interested to know how much input teams had in the rule configuration before this was foisted on them.

>Don't spend your time hunched over servers. Spend it doing things you love with people that matter to you

Who are you to tell people how to spend their time? Let people have hobbies ffs

Did you not read the comment he wrote? It's straightforward

Says who?

None of this stuff is remotely impressive from an engineering perspective. You pay a service to provide code for you. That's existed for a while now.

s/(agentic|llm|vibe) coding/outsourcing/g

FWIW, @ is a shortcut for HEAD in Git.

Good luck finding much of that creativity you value so much when those creative types are preoccupied with meeting their basic needs.

Everybody loves NIH until what gets invented is dogshit. Seriously, it's easy to romanticise the idea but wait until you have to work on something that evolved over a decade without any refactoring or documentation, and worse, the author is a lifer who couldn't ever imagine that their code could use improvement. I'll migrate to whatever silly API react router has cooked up this year over living that again, thanks.

>downloading files to their local machine, making changes, then emailing git pushing them up to be approved

Forgot the part about building and running the software.. The argument is even dumber with that omission higlighted.

I am not allowed to install legitimate development tools..

I have a super neat one but it's on my work machine. Not strictly a one-liner but definitely a CLI QoL improvement. It allows me to type a partial command, for e.g. up to where a file path might be, hit a hotkey to invoke (e.g.) fzf, and finally have fzf's output inserted where my cursor was in the command. Uses some vars that readline exposes. I haven't taken it beyond inserting paths yet, but you could imagine you could do a lot with inserting arbitrary output into a command you are midway through typing. I'll reply to this when I have it on hand.

Semi-related: if I want to do a little side quest, maybe pop over to another repo or git worktree for a quick look, I'll drop into a subshell just by running bash before cd-ing. Then I just exit that shell (alias q=exit) when I want to return back to the original dir and context.

>The good managers I work with (and in my role I work with many) are definitely leaders in the traditional sense.

It's a fine opinion to have, but on matters like this, I'm more interested in the opinions of those who are being lead. Plenty of leaders love to think of themselves as great leaders.

It's because our profession seems to attract a number of intellectually insecure people who thrive on these little puzzles and the associated minutiae as a means of feeling a sense of superiority. They all think they've figured it out: the best way to tell if someone is a Good Dev or a Shit Dev. Of course, administering the test, there's no way they could possibly be anything but the Good Dev. It is embarrassing. Don't believe me? Why can't they help but blog about it?

I cut my dev teeth in a financial institution so I'll concede I'm biased away from risk, but devving directly on the prod DB, not having a local enviroment to test changes against, and worse: literally no backups.. it screams wreckless, stupid, cheap, arrogant, and immature (in the tech sense). Nothing I'd like my name against publicly.

>This isn’t evolution. It’s self-inflicted complexity. And we’ve normalised it – because somewhere along the way, we started building websites for developers, not for users.

We started building websites for the marketing department, not developers or users.

>nothing about the post suggested that.

>[they] are good at spinning answers to make everyone hear what they wanted to hear.

To me that definitely reads like the original comment was alluding to an ability to bend the truth or frame things in an advantageous way, which is essentially lying's brother, manipulation.

Besides, politicians have earned their reputation a hundred times over. Good luck convincing anyone that it's unfair to suggest politicians are liars.

I can't help but feel these hyper optimistic takes on AI are just pure naïveté. Does one really think that redirecting the earning potential of a good chunk of the white collar population into the pockets of the already-wealthy is going to end well? I can't see a soft-landing scenario.

>"We, as the producers of this technology, have a duty and an obligation to be honest about what is coming,"

Thank you for being so honest Mr CEO. What a great guy.

/s

Think that's the problem. The people who have the keys to the money to do the hiring are often off the tools and have no real grounding in the capabilities of the current generation of LLMs. They make decisions about how much to or not to hire based on the junk they see from the Elon Musk types.