Tanel Mae’s Post

Last Tuesday, I shared a blog post titled 'What is platform engineering and how can you do it effectively?'. Missed it? No problem! I’ve put together a brief summary for you below. Check it out!

'ell' is a beautifully simple take on prompt engineering. Provides you with a concise way to iterate on prompts and nice tools to capture/visualise all the requests that come back from your llm of choice. You can find out more in my video on it: https://lnkd.in/evqEr2KC

About to do my last talk of the week with David Anderson and Roland Barcia. Balance consistency and developer freedom with platform engineering.

Check out our latest blog post that summarises Abby Bangser's webinar, "The #1 Platform Engineering Problem You've Never Heard Of: Platform Decay (Webinar Recap)" https://lnkd.in/eTbsUf9m

The entanglement only facilitates the spotting of errors but not their correction. https://lnkd.in/dV9jpf-G 🚀 Explore more with Interesting Engineering! Check out our YouTube channel and subscribe: https://ie.social/V9yxY

Dive into Model-Based Systems Engineering with a free self-paced System Composer Onramp course where you will gain practical skills in constructing system architectures and connecting them to requirements, all through interactive, self-paced online modules. https://spr.ly/6041YclPf

The state of prompt engineering in 2024. We’ve evolved beyond complex tricks, patterns or full time prompt engineer roles and are officially in the golden age of “no yapping”

No known bugs is an engineering manifestation of our principle "When this baby hits 142kph...". Finding the fastest speed of delivery that we can maintain. Yes everyone wants new features, but, in reality they need reliable software more. Our extremely low customer churn is testament to this. We do everything we can to not let our customers down or embarrass them. They repay us by partnering for the long term. This in turn allows us to make long term bets to deliver even more value to them. Positive feedback loops like this are the foundation of long term success.

One of the biggest ironies of software development: firing all the engineers that do nothing will probably destroy the company. But firing all the engineers who write 10x more code than everyone else will probably boost performance by at least 20%

My timeline across all social networks and many of the news letter I follow are full with mentions to "ghost engineers". All this started with a Stanford researched that published a report (not peer reviewed) stating that 1 out of 10 engineers do not contribute, based on their commit activity. I will not get into the red flags of the study, or the sanctimonious tone of some of the author's comments ("this has to stop!") . That would be too easy. I will just weight into the non-sense of measuring engineer's contributions by commits. Most senior engineers contribute by driving design discussions, giving feedback, helping management define and evaluate initiatives, hiring, and mentoring. This is glue work. It is as valuable as code contributions.