It is a source of continuous delight to watch the AI community rediscover the fundamentals and the dynamics of software engineering as they take those things and embellish them with AI adjectives, making them sound all fresh and new and sparkly while in truth, those fundamentals remain, well, fundamental.
Remove AI from the discourse below, and what Andrew promotes are things one heard all the time as we saw - starting decades ago - the transition from assembly language to FORTRAN and COBOL, from structured to object-oriented, from waterfall to agile.
The past, as is said, does not repeat itself but rather rhymes.
Don’t get me wrong: I celebrate what Andrew et al are doing: developing software-intense systems that are meaningful and that endure requires intention and discipline, and I embrace that.
Two dangling threads before I close:
I don’t grok the semantics of “traditional teams”. The cosmos of computing is so wide and deep and diverse and crosses so many domains, I conclude that “traditional teams” is what one says when their experience is in a relatively narrow space, and they are witnessing a shift from what they grew up with in the Valley in particular, where web-centric systems of global elastic scale remain the primary focus.
Second, I am dismayed at the focus on speed. If you are driving head long Thelma and Louise style toward an IPO then certainly speed will be a critical factor. But for most of the domain of computing, for systems that are meaningful and that endure, other factors are far more important: correctness, repeatability, safety, maintainability, these dominate, and as such, don’t be distracted by the noise and smoke and heat and light of an AI first style that may get you out of the starting gate quickly, but will fail you in the ultra marathon of most development.
Software engineering has always contained two distinct modes of work. The first is developmental: taking a clearly specified concept and translating it into a reliable, working system.
This is no longer the bottleneck. AI tools like Claude Code and Codex have effectively solved it.
The second mode is research. Here, the problem itself is undefined. The task is not to implement a solution, but to discover what the solution should be, new abstractions, algorithms, architectures, and ways of reasoning about computation.
This layer resists automation because it depends on framing, taste, and deep conceptual synthesis rather than procedural construction. While AI can assist exploration, it does not yet originate the governing questions that drive genuine breakthroughs.
For that reason, software engineering is unlikely to disappear. Instead, its center shifts toward the research frontier.
Coffee before breakfast spikes your stress hormones and sets you up for a crash.
Many people kick off their day with a strong cup of coffee for that instant energy boost, but sipping it on an empty stomach—especially right after waking—might be counterproductive and even counterproductive to your body's natural rhythms.
Upon waking, cortisol (your primary stress hormone) naturally surges to help you feel alert and mobilize energy. Adding caffeine during this peak window, without any food to buffer it, can amplify this response more intensely than necessary.
While some popular claims link this to dramatic cortisol spikes leading to anxiety or crashes, the key evidence from the University of Bath's research focuses on metabolic effects: consuming strong black coffee before breakfast (particularly after a disrupted night's sleep) impairs blood glucose control, raising post-meal blood sugar responses by about 50% compared to eating first.
This creates unnecessary metabolic strain, contributing to energy volatility, potential jitters, heightened stress sensations, and that familiar mid-morning slump.
The University of Bath study (published in the British Journal of Nutrition, 2020) didn't directly measure cortisol but highlighted how this coffee-first routine disrupts glucose/insulin dynamics—effects that align with broader reports of caffeine interacting with stress pathways and exacerbating morning hormonal fluctuations in some individuals.
A simple tweak makes a big difference: eat something small first (even a handful of nuts, yogurt, or fruit) to provide a biological cushion. Food slows caffeine absorption, moderates any amplified hormonal or metabolic response, stabilizes blood sugar, and lets the caffeine deliver clean focus and alertness without the unwanted side effects like jitteriness or crashes.
In short, timing your coffee after a bite turns it from a potential stressor into a reliable ally for a smoother, more balanced start to the day.
[Betts, J. A., Richardson, J. D., Chowdhury, E. A., Holman, G. D., Tsintzas, K., & Thompson, D. (2020). Glucose control upon waking is unaffected by coffee consumption prior to a disrupted night’s sleep. British Journal of Nutrition]
@smoet Menej SK politiky a viac medzinárodných a hlavne (aj) pozitívnych tém. Preto som viac-menej prestal počúvať dobré ráno a prešiel na Vinohradskú 12.
Pre mňa zatiaľ slovenská momentka roka 2023.
Ivan Kamenec, špičkový historik holokaustu a Slovenského štátu, ktorý sa ako 6-ročný musel ukrývať v bunkri pred nacistami, dnes na proteste pred dverami budovy SRo, kde sa konala diskusia Uhrík-Kotleba.
(Foto: FB/Zabudnuté Slovensko)
The Sphere at The Venetian Resort in Paradise, Nevada, has an exosphere made of LED light panels which is visible from several miles away.
It's being tested in these days and it's quite stunning
[read more: https://t.co/VViYhUIx3G]
@MAKA32165595@Robo_Kazik Mal som a vlastne ešte mám aj nerezovú platñu asi 5mm hrubú a tu som rozpálil na wok horáku. To bolo celkom rýchle a funkčné ale skončilo to výmenou plynovej dosky za indukciu 😂 Kameň som skúšal no to sa pekelne dlho nahrievalo v rúre.