I’m getting pretty tired of this so here it is: running on Kubernetes is not modernizing your application. Moving an app to a different framework is not modernizing it. Solely chopping your app into 20 is neither microservices nor modernizing. Building a better app is.
I wrote an article with @stilkov and @moonbeamlabs about why it is still a good idea to use the classic architecture of the web with only moderate amounts of JavaScript.
Now available in English!
https://t.co/xDR0UKCEq3
This is an outstanding gem by @simonbrown if you're looking for how to structure a (Java) codebase for maximum component decoupling. I've been following style #4 for over a decade and it's never disappointed: https://t.co/ILi79p2qMH
The practices and patterns you see may not seem sensical to you, but they did to some person at some time. In such cases, curiosity will serve you better than judgement.
#7RulesForChange#NonJudgement
X : Any chance we can meet for coffee?
Me : Virtual or in person?
X : In person.
Me : Whereabouts?
X : I'll be in London next month.
Me : Ok, A coffee shop in London Hythe.
X : Where's that.
Me : About 70 miles away.
X : Something a bit more local?
Me : Hythe is local ... to me.
Designing for the web ought to mean making HTML and CSS. When that's getting too hard to do because of complexity sprawl of JavaScript, it's time to revisit your assumptions of how to work. https://t.co/CjlRcwi4Sz
One element is often forgotten, when people think about agile methods: "Before we can tap into the benefits of teamwork, we need to build a team." (@estherderby)
There's more to "fixing" legacy software than providing test coverage and refactoring code. It's also reducing complexibility, simplifying build process and infrastructure, creating monitoring, logging, alerting, CI, CD, static code analysis... and so on. Exhausting but rewarding
Test-driven development and infrastructure coding should be equally important, @jonashackt argues in his new blog post: https://t.co/cvr4bU4a5O #ansible#molecule#tdd