Sabitlenmiş Tweet
DaShaun
24.3K posts

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

Tomorrow: @cat_edelveis and @dashaun on hardened images for #Java services.
Less CVE noise, less patching churn, fewer rebuild loops, and a base image that does not create half the problem in the first place.
📅 Thursday at 14:00 CET
English
DaShaun retweetledi

@TheAhmadOsman That's what I thought at first too.
I have an NVidia 5090 and a MacBookPro M4 with 128GB.
What test would you have me run? Actually, do you want to work together on something, with real metrics to back it up?
GIF
English
DaShaun retweetledi

One thing I keep seeing in modernization projects:
Classic Java applications, for example, Swing apps, are often much easier to reverse engineer than supposedly modern systems.
Why? Because the behavior is still visible in one coherent codebase. Screens, workflows, validations, and state changes can often be traced quite directly. That makes it possible to derive System Use Cases and use them as the foundation for a modern implementation.
SPAs with microservices are usually a very different story.
What looks like one business workflow from the user’s perspective is often scattered across frontend code, APIs, multiple services, events, and databases. The result is fragmentation. And that fragmentation makes reverse engineering much harder, slower, and less reliable.
This is something many teams underestimate.
Modern architecture does not automatically make modernization easier. In practice, old Swing systems are often ugly, but understandable. SPA and microservice landscapes may look more modern, but they are often far more difficult to reconstruct when you need to understand the actual behavior of the system.
That is exactly why deriving System Use Cases from legacy desktop applications can work surprisingly well, while doing the same for fragmented SPA and microservice systems is often painful.
Have you seen the same in your modernization projects?

English
DaShaun retweetledi

GitHub #CopilotSDK for #Java is now official, in Public Preview, and has a new release!
github.com/github/copilot…
English
DaShaun retweetledi

LLMs are doing it the hard way - with John Willis and @starbuxman
#coffeesoftware
Watch more: youtube.com/live/E_VcorY7s…

YouTube
English

Models and benchmarks: genius or failing students?
With John Willis and @starbuxman
#coffeesoftware
youtube.com/live/E_VcorY7s…

YouTube
English

"Spring is a great example of an abstraction that created abundance" John Willis and Josh Long share thoughts #coffeesoftware
Watch more: youtube.com/live/E_VcorY7s…

YouTube
English
DaShaun retweetledi

- Meet James Gosling
- Creator of Java
- Built his first computer from scratch as a teenager
- Loved math, science, and tinkering with electronics
- Preferred experimenting on his own rather than traditional classroom learning
- joined Sun Microsystems and noticed a major problem
- Programming languages were complex, unsafe, and hardware-dependent
- Code couldn’t run easily across different machines
- Many projects failed due to system incompatibility
- got Frustrated with these limitations
- Created a new language called “Oak”
- They wanted simple, catchy, and energetic name
- The team was drinking coffee during brainstorming ☕
- so Later they renamed it to Java
- he wrote the original Java compiler and virtual machine himself
- designed it to be Simple, Secure, Platform-independent
- it became one of the most influential programming languages in history
- Widely used in: Web applications, Android apps, Enterprise systems, Banking software
- Adopted by millions of developers worldwide
- earned the nickname as “Father of Java”
- literally changed how software is built across the world.
Absolute legend.


English

Software and Schrödinger's cat - with John Willis and @starbuxman
Watch more: youtube.com/live/E_VcorY7s…

YouTube
English

I just claimed my .agent domain and joined the .agent community! get yours now and help shape the future of autonomous agents #BAN94SY2" target="_blank" rel="nofollow noopener">agentcommunity.org/join#BAN94SY2 @agentcommunity_
English
DaShaun retweetledi

This is WILD.
A secret workplace war just broke out in China and it has gone fully viral on GitHub.
Companies started ordering their workers to document all their knowledge as AI "skill files."
Why? to replace those same workers with AI but workers figured out the plan fast so they fired back.
Someone built a tool called colleague.skill, software that scrapes a coworker's chat logs, emails, and work docs from Chinese platforms like Feishu and DingTalk, then clones them into an AI agent.
The idea was savage, digitize your colleague before they digitize you, hand the AI clone to the company, and watch your coworker get laid off while you survive.
A real GitHub project that exploded in popularity in days but then someone else entered the chat and changed everything.
A developer released anti-distill.skill, a tool that takes the skill file your company forces you to write, then strips out every piece of real knowledge before you hand it in.
The output looks perfectly professional, totally complete, impressively detailed but every critical insight has been secretly removed.
Your company gets a hollow shell while you keep the real knowledge locked away in a private backup.
The tool even has three intensity levels, light, medium, and heavy depending on how closely your bosses are watching.
Companies across China have been building AI digital twins of departed employees, feeding their old chat histories and documents into large models to produce clones that keep working after the humans are gone.
One verified case is that an employee left, and their replacement was literally an AI trained on every message they ever sent.
The anti-distill tool went viral on GitHub within hours of being posted, racking up stars faster than almost anything trending that week.
The implications reach far beyond China's borders.
Every knowledge worker on earth now faces a version of this question, when your company asks you to document your process, they may be building the tools to replace you.
English
DaShaun retweetledi









