RT @shanselman: Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, so….

RT @LeVif: CARTE BLANCHE | Des professeurs de l’ULB dénoncent le «syndrome du déni d’antisémitisme présent» à l’université .

In the quality assurance hierarchy we should make sure to add one line of defense even more fundamental than unit tests: The best quality guarantee is if you can write your program in such a way that error states cannot even exist.

RT @BMWK: Der Terrorangriff der Hamas auf #Israel ist jetzt bald vier Wochen her. Vieles ist seitdem passiert, die öffentliche Debatte aufg….

Checking out @obsdmd - it has a bit of an emacs org-mode feel to it which I appreciate a lot.

Senior leadership did the analysis: The root of the problem at XYZ Corp was a lack of clearly defined value statements that underpin the company’s unique culture! Problems like this demand the corporate weapon of choice to jump into action: The Workgroup.

“When the winds of change blow, some people build walls and others build windmills.”.

I’m actually looking forward to trying this out.

I am certainly not the only one observing that the workplace has a tendency to make any word that described an interesting or innovative concept almost meaningless over time. On linguistic entropy and chinese whispers. 👇.

Oh, wow, Google’s odbl licensed building data set looks pretty neat. How difficult would it be to load these into @mapwithrapid for quick editing? 🤔.

Records are part of the Java language since version 14. They are a useful feature for types that primarily capture data and avoid some of the boilerplate that Java is famous for. How far should we push their use?.

Hey Twitter folks. Hot tip: Try searching for “Exponential Backoff with Random Jitter”. You're welcome! 😉.

RT @garybernhardt: 1960s: "COBOL will let non-programmers make the software!". 1980s: "4GLs will let non-programmers make the software!". 2….

RT @MarcJBrooker: Simplicity is a property of systems. It's always possible to make components simpler by pushing the complexity elsewhere….

One particular issue with the salary negotiation process is that candidates unable to approach a negotiation from a position of strength are at a disadvantage. Here is an alternative mechanism that could level the playing field:

When designing distributed systems, we sometimes think of latency and availability as two technical dimensions to balance out in our designs. I would like to argue that a more useful perspective would be to see them as two sides of the same coin.

DevOps is in part about breaking silos: “You build it, you run it”. Why don’t we apply the same arguments to other organisational fault lines: “You ask for a feature, you build it”. Or “you build it, you sell it”?.

The criticism that text generated by AI is basically plagiarism seems to be conceptually easy to solve? Have an indexed DB of source material, match on similarity and reject matches that are too similar & add references as appropriate. A bit like a human would deal with it?.

But…. class HttpInterface extends NetworkInterface {…}. can always be transformed without loss into. class HttpInterface implements HasNetworkInterface {. NetworkInterface getNetworkInterface();. ….}. So composition is just as polymorphic, right?.

I know I know… “not the same thing”… but reading people worried about AGI while watching Roomba getting stuck while trying to navigate the apartment IS kind of funny.