DaShaun

24.4K posts

DaShaun banner
DaShaun

DaShaun

@dashaun

Husband, father, volunteer, athlete, continuous learner. Tweets are mine. Spring Developer Advocate @VMwareTanzu #JUICE #LiftAsWeClimb @Testcontainers Champion

KC MO Katılım Mart 2008
4K Takip Edilen5.5K Takipçiler
Sabitlenmiş Tweet
DaShaun
DaShaun@dashaun·
Each new CVE is the dinner bell for bad actors all over the world. If they don't act on it immediately, they might not get dinner.
English
1
2
16
4.7K
DaShaun retweetledi
CrAIg Walls
CrAIg Walls@habuma·
Building AI agents with Java and Spring? I’ve been sharing a ton of practical Spring AI recipes lately, and now there’s a 45% discount on my Spring AI book too! (Seriously, folks. 45%. That’s no hallucination.)
Manning Publications@ManningBooks

AI tooling has largely lived in the Python world, which can add friction for teams building with Java and Spring. Spring AI helps remove a lot of that extra integration work by bringing model APIs, embeddings, vector databases, retrieval workflows, and agentic capabilities directly into the Spring ecosystem. @habuma's Spring AI Recipes shows the agentic capabilities and more with hands-on examples: hubs.la/Q04gHy9F0 And you can get 45% off his book, Spring AI in Action, with code habuma: hubs.la/Q04gHx8Y0

English
0
3
18
1.9K
Bruno Borges
Bruno Borges@brunoborges·
Sorry mate. You can't be using AI to draft a tweet like this, complaining about how AI is creating a dangerous generation...
Akshay Saini@akshaymarch7

I think AI is quietly creating a dangerous generation of software engineers. And nobody is talking enough about it. A lot of developers today can build things faster than ever before. But fewer developers actually understand what they are building. That’s the scary part. I recently noticed something while talking to students and engineers. People can now generate: 0. React components 1. APIs 2. backend architecture 3. SQL queries 4. Docker configs …within seconds. But the moment something breaks unexpectedly, many get completely stuck. Because debugging requires understanding. And understanding takes struggle. Earlier, when we used to build things manually, we would suffer through: 0. weird errors 1. broken deployments 2. dependency hell 3. state management bugs 4. performance bottlenecks At that time it felt painful. But that pain was actually building engineering intuition. AI removes a lot of friction. Which is amazing. But it can also remove the learning. And I think this is where the gap between “developers” and “engineers” will become very visible over the next few years. The developers who survive AI won’t be the ones who can generate code fastest. It will be the ones who can: 0. think deeply 1. debug systems 2. make engineering decisions 3. understand tradeoffs 4. simplify complexity Code generation is becoming cheap. Judgement is becoming expensive. That’s probably the biggest shift happening in software engineering right now.

English
1
0
8
1.1K
DaShaun
DaShaun@dashaun·
@ibuildthecloud Yes! Build a coding agent that works for you! There is plenty of room in the space!
GIF
English
0
0
1
41
Darren Shepherd
Darren Shepherd@ibuildthecloud·
The problem is I can personally build a better coding agent... Should I just throw my hat into the ring? Take on the world? Why not?
English
12
0
27
3.2K
DaShaun retweetledi
Joshua McKenty
Joshua McKenty@jmckenty·
Has anyone made an agent-friendly version of init.d /sysinit yet? It feels like the exec/ps/kill world is old and needs to die. Process trees are different when agents own the process lifecycle, and the supervisor pattern needs to evolve. Thoughts?
English
0
1
0
389
DaShaun retweetledi
Josh Long
Josh Long@starbuxman·
Good morning from CodeRemix.ai ! What are you building today?
Josh Long tweet media
English
5
1
27
1.7K