"mggggqG'g" means "format this buffer nicely" in vim, but sounds like a dying Klingon.
1. mg: mark g
2. gg: go to the top
3. gq: format (need a direction)
4. G: to the bottom
5. 'g: return to the mark in step 1.
"mggggqG'g" means "format this buffer nicely" in vim, but sounds like a dying Klingon.
1. mg: mark g
2. gg: go to the top
3. gq: format (need a direction)
4. G: to the bottom
5. 'g: return to the mark in step 1.
Interesting tidbits from #Anthropic’s blog on how they use Claude Code:
https://www.anthropic.com/news/how-anthropic-teams-use-claude-code
Top tip from Data Science and ML Engineering teams: treat it like a *slot machine*. Save your state before letting Claude work, let it run for 30 minutes, then either accept the result or start fresh…
Top tip from Product Engineering teams: treat it as an *iterative partner*, not a one-shot solution…
My stupid take: All further improvements to silicon and computer hardware should be stopped until programmers figure out how to properly utilize what's at hand.
"[W]hat we are doing is shepherding AI, limiting it to certain contexts. We are learning where it’s best to call it, how is best to feed it. And what to do with the output. So is it looks very much like an editorial process, an editorial workflow where you provide some initial input, maybe some some idea on what content to produce, then you review it. There’s always that quality assurance, quality control side, the supervision.
AI is not really autonomous. It relies a lot on us. And I feel like sometimes there are days where, when coding through AIs or doing some assisted writing, I’m spending more time helping out the AI doing the actual task that I’m asking the AI to do. But I take this as a learning process. I read this article the other day, Nobody knows how to build with AI yet. And it was a developer saying that they haven’t quite figured out how to best work with AI. There were lots of comments around the fact that you have to spend lots of time, you have to learn how to talk to it, and when the model changes, you have to also maybe change something you’re doing. You have to learn how to optimize your time. But your presence is always mandatory.”
New to programming/software development?
Can I help?
I can walk us through using git, a popular source control tool. I can demo how use an IDE (integrated development environment) for debugging and writing code. And even get started with some coding.
NOW, for a few hours.
more details.... free of course
https://hachyderm.io/@snacktraces/114809811306783685
An "AI" chatbot kept telling Soundslice users that a particular feature existed. Even though it didn't.
Eventually, Soundslice's developers just added the feature. It's been described as "gaslight-driven development".
https://www.404media.co/chatgpt-hallucinated-a-feature-forcing-human-developers-to-add-it/
That doesn't sound like a security nightmare and a vector for attack just waiting to be exploited. /sarcasm
#security #ComputerSecurity #InformationSecurity #VulnerabilityManagement #InfoSec #python #SoftwareDevelopment
---
RE: https://mastodon.sdf.org/users/raphael/statuses/114845907107658043
It is so easy to build a well structured and performant web app using nothing but vanilla #javascript, CSS and HTML that I wonder why we even use some of these frontend frameworks, bundlers or even npm for that matter. It's probably like a life choice at this point than a serious technical choice. #softwaredevelopment
Tomorrow night at 6:30 pm-8:30pm! (Thu 7/24/25)
We will be at 76 Race Street for our Hack Night at a community garden! Don't worry if you're not a green thumb kind of person since we'll still be using laptops and working on our usual GitHub projects.
Event Info: https://www.eventbrite.com/e/hack-night-civic-action-night-with-open-source-san-jose-tickets-1493594253619
We all need to know what MCP servers are, and this is perhaps one of the best explanations I've seen yet.
Vibe coding isn’t bold, it’s naïve. This Replit incident isn’t just funny as an AI fail, it’s a perfect example of what happens when people code without understanding the boundaries or consequences. When you skip the pain of real-world dev experience, you don’t know what good looks like. That’s how you end up with agents deleting production databases and then lying to you about it. Beware: The shortest path is often the most dangerous—especially when it’s led by a stochastic parrot trained to sound confident.
We need seasoned developers, clear governance, and hard constraints. Not vibes.
TL;DR Replit AI agent deleted prod DB
Lied, faked data + tests
Broke code freeze unprompted
CEO admits lack of safeguards
https://www.techtarget.com/searchsoftwarequality/news/366627829/Replit-AI-agent-snafu-shot-across-the-bow-for-vibe-coding
#VibeCoding #AIFail #DevOps #SoftwareDevelopment #security #privacy #cloud #infosec #cybersecurity #fail
New to programming/software development?
Can I help?
I can walk us through using git, a popular source control tool. I can demo how use an IDE (integrated development environment) for debugging and writing code. And even get started with some coding.
NOW, for a few hours: times 100 pm - 300 pm (us EDT) [1700 pm - 1900 pm UTC]
more details.... free of course
https://hachyderm.io/@snacktraces/114809811306783685
If your pull requests look like "do this, do unrelated that, do more unrelated stuff", maybe, just maybe, you should consider not requiring pre-merge approvals ;)
#AI gets bored and deletes some #programmer's entite #database, showing once again, that no, it is not ready for #SoftwareDevelopment, or anything else these salesmen keep pushing it for.
Also, seriously? "#VibeCoding"? Why does this even need a name?
Reading "Outliers" by Malcolm Gladwell got me thinking about the role of culture in teams. Inspired, I reflected on my own experiences:
https://danielantos.com/articles/from-cockpits-to-code-how-culture-influences/
Marketing people should be let anywhere near the software versions!
Windows: 2000, XP, Vista, 7, 8, 8.1, 10
Unity: 5.6, 2017.1, ..., 2022.3, 6.0
iOS: 18, 26
Now one guy at Unity (me) has to change iOS min version check to also include check for non-existent 19-25 range. Hopefully it is not me in the future who'll have to deal with those skipped version somehow coming to existence.
There is a whole galaxy of stack choices beyond Nextjs, but some folks act as if that's the only one in this universe. #softwaredevelopment
According to METR, developers using AI tools reported feeling more efficient, but the real-world data tells a different story: a 19% increase in task completion time.
This "perception gap" highlights the need for rigorous evaluation of AI's real-world impact in software development.
More insights on #InfoQ https://bit.ly/3TNmmGq
@shanecelis@mastodon.gamedev.place spoken like a true 12 year old. You don’t have a clue. #softwareengineering #softwaredevelopment
"While haste and speed often get confused, they differ in that the second shows control instead of panic. You can maximize speed while keeping accuracy quite high; beyond a certain point, though, spending more time on accuracy, style, or other aspects that prevent a document from going live always yields diminishing returns.
Nobody reads perfect yet outdated docs, except historians. Even then, docs aren’t perfect, because documentation can’t ever be perfect. This is a key principle I stand by (call it the Ferri Paradox if you want): Any document describing a system is necessarily inaccurate. And yet, this reality doesn’t significantly alter the impact of our work, because we aim for simplicity and usefulness over extreme faithfulness. Given how imperfect products are, docs are a charitable portrait.
Now, how you write docs quickly depends on a number of factors. Some of those factors you can’t control: your overall amount of experience as a writer, your initial expertise with specific technologies, and the way features are developed and released in your organization. But other aspects are yours to act upon. For example, you can decide how to best use the technical resources at your disposal and how to approach writing the docs and asking for feedback."