Allan Frese

Let's talk about Trust. Recently I just finished my skipper courses, and you know what - it's so much a software development. You're - a cross-functional team of 2-8 people - with a delivery idea of moving the vessel from point A to point B. But yet, that's an extreme sport - and as with every extreme team activity - Trust is key to success. A team member has the Trust if - believe other members are doing their best in their work - believe other member's estimations/promises are true - believe other members will raise a flag once trouble appears > We can fail, but fail quickly and learn. But how do you build that in the team? The first thing you do - you become such a person. You always do your best. You try to keep your word and promises. You fail and talk about that openly. You are - the Trust deliveryman. > As a leader, you need to trust your team first to be trusted. So what do you think? - Do you have a Trust-specific task in your backlog? - How do you measure the Trust in your team? - Did you have an experience where a lack of Trust became a blocker? inspired by https://lnkd.in/dGQCPi9v #LifeIsASoftwareDevelopment

19

2 Kommentarer

Good opportunity

1

The video for my talk at the awesome AWS Community Nordics community day in Copenhagen is now available on YouTube! You can watch it at the link below! Please also check out the rest of the videos of the awesome talks from the incredibly talented people I was lucky enough to share a stage with on the AWS Community Nordics YouTube channel! #AWS #AWSCommunity #Serverless #EventBridge

16

I've been doing Codewars katas in Rust to try an cement my (quite limited) knowledge and really thought I was on the right track with the top solution! The problem was to return the sum of all the numbers between a and b. - So I added a mutable sum variable on line 5. - Returned 1 value if they were the same on line 6. - Determined which value was highest/lowest on lines 9-10. - Created an inclusive range between the two on line 12... Then forgot the basics of coding on line 13! I'd been so focused on using the syntax of my new language that I forgot the basics! I failed the very first test! That had passed the values 0 and 1 - should be simple right? I think what I'd been thinking of was mapping over an array in JavaScript, or something..., because I know there are methods like next() in Rust. I thought I was being clever - how do you add one value to the next. 🤔 I ran the code, and was totally puzzling over how 0 and 1 could somehow equal 4. Then I remembered I wasn't using an array, but a simple for loop. One that, for those params, would return 1 for the first iteration, then 3 the last. 🤦‍♀️ And, of course, I didn't figure that out right away. Nope, me, being me, had to question my Rust specific code. So don't forget the basics, like little old me!

16

This is the latest episode of Spilling the Source: https://lnkd.in/ekZXrest If you contribute to an OSS library, or are simply enthusiastic about one and would like to come on and talk about it then please get in touch, or reply to this.

2

Just got back from an inspiring CTO dinner at Google Stockholm! While I might not be a CTO yet (future CTO vibes, anyone?), it was an incredible chance to learn from the best. The night wasn't just about fancy dinners (although, let's be honest, those were pretty great too). We dug into the nitty-gritty of technical leadership, the challenges that come with it, and how to navigate them. But the true goldmine? Picking the brains of Google's engineering wizards about real-world applications of generative AI that are driving serious business value. This is the kind of info that separates the good from the great, and I'm itching to put it into action! #FutureCTO #GenerativeAI #GoogleCloud cc: Oscar Söderlund, Mark Shine Jason Quek

53

4 Kommentarer

2024 is nearly over. Did you already invest in yourself? Maybe you still have budget left for your personal development? If you want to build up your skills on product development, I have two great recommendations for you - both for product, design, and engineering people: 1️⃣ November 6+7 the Tech Leadership Summit will take place in Zurich, co-located with the renowned Product Management Festival. One ticket buys you access to both! My discount code "DiscountSpeakerTLS" will cut the price by 20% - but the value stays at 120%! 2️⃣ November 13+14 will see the Digitale Leute Summit in Cologne. You can learn from amazing talks, but also join full day content-packed workshops. My discount code "DLS24JAN20" will give you 20% off of tickets. Spoiler alert: 2025 will also bring its challenges. 😉 Set yourself up for success! The direct links are in the comments. Disclaimer: Okay, okay - I will also give talks at both, but you can easily go to the other talks instead. 😘

57

6 Kommentarer

I recently had a conversation with Mariia Vain, a Staff Software Engineer at AgencyAnalytics, about one of the most critical skills for Staff+ engineers: prioritization. As Mariia pointed out, there will always be countless things you could be fixing, improving, or building. The challenge isn’t in finding what to work on but in narrowing it down to the 2-3 things that will have the most impact over the year. This can involve engaging in deep conversations and interviews with engineers across different areas, identifying opportunities where solving one issue could have rippling effects across teams. Using data like performance metrics, security reports, and reliability stats to back up these decisions can also make a stronger case for why a particular direction is chosen. Setting up recurring meetings with focused teams—like a backend council or guild—can help align on priorities and gather insights from those closest to the work. At the end of the day, it’s up to the Staff+ engineer to make the final call and communicate this clearly to engineering leadership. While ensuring that all voices are heard, sometimes you need to disagree and commit in order to move forward. How do you navigate prioritization in your role? I’d love to hear your strategies and experiences! If you're a Staff+ Engineer I'd love to connect: https://lnkd.in/gKT7unhC

9

𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐜𝐢𝐞𝐬 𝐯𝐬 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I've worked in 𝐬𝐭𝐚𝐫𝐭-𝐮𝐩𝐬, IT 𝐜𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐜𝐢𝐞𝐬, from niche to mid-sized to Large, the IT dept of non-software companies, and software 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 companies. Let me share some 𝐩𝐫𝐨𝐬 and 𝐜𝐨𝐧𝐬 about working in the different ones. 𝐂𝐎𝐍𝐒𝐔𝐋𝐓𝐀𝐍𝐂𝐈𝐄𝐒 I'll be honest: consultancies have a strong hold over the tech sector in Norway, as there simply isn't many or any big software product companies to speak of. Only small/start-ups. So, a lot of the talent pool is working in consultancies. I eventually left my home country to work in a Software 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 company 🏡 💼 🛫 🌍 😁 𝐏𝐫𝐨𝐬: ➕ Work with experts & technology specialists ➕ Access to great training programs, technical and non-technical ➕ Exposure to many different industries! - Public and private sector. Retail, airports, energy, agriculture, government - etc! 𝐂𝐨𝐧𝐬: ➖ Tech > Problem-solving: You're sold as a <insert tech> dev. ➖ Process & Red tape - Pre-defined deliveries/contracts means things can be slow or difficult to change ➖ Little to no ownership of the product ➖ Certifications > Impact - Consultancies wants you to be easy to sell. Certs works as a proof of your skills. 𝐏𝐑𝐎𝐃𝐔𝐂𝐓 𝐒𝐭𝐚𝐫𝐭-𝐮𝐩𝐬 I had an internship in a start-up as a CS student. This experience was invaluable. I later worked as a software engineer in a start-up, and worked on some very cool projects. Had a lot of fun, learned a lot. 𝐏𝐫𝐨𝐬: ➕ Fast paced, not boring ➕ You can and must wear many hats ➕ Could be career making 𝐂𝐨𝐧𝐬: ➖ Little to no structure or process ➖ Potentially nowhere to grow ➖ A big risk that might not pay off. If you're in a start-up, make sure to get something out of it even if the start-up doesn't succeed. 𝐍𝐨𝐧-𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I worked in television(!) As a Business Intelligence dev & analyst. Basically a data engineers & Data scientist. ➕ Can have big impact on the product/business ➕ Exposure to potentially interesting domain ➕ Help non-technical stakeholders ➖ Not solving for the core business, not prioritized ➖ Slow to adopt new tech. ➖ Lonely - No dev community. Things like Code quality, CI/CD, DevOps, DevEx... is up to you/your dept, or nonexistent. 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I might be biased here as I currently work in a Software product company, something I wanted for a long time. ➕ Have a big impact on the core business and or for customers ➕ Win by solving interesting & challenging industry problems in smart ways over use <insert tech> by all means. ➕ Ownership of product over time ➕ Career growth opportunities ➖ Working in a high performance environment can be stressful ➖ Bias for action or bust ➖ Learn how to deal with Ambiguity or have a bad time Please let me know what you think of this!!!

31

9 Kommentarer

I had a interesting conversation with Florian Gamper yesterday while in Berlin around Meetups vs Roundtable events. Do you find with meetups, you gravitate to the same people, have the same conversations and leave with a slice of pizza of course or are you meeting new people etc. Is Roundtable’s more beneficial, having someone facilitate the topics of conversation you are interested in, break out sessions to discuss these topics, smaller groups so you meet everyone. Really interested to get other people’s thoughts on this? #roundtable #meetups #berlin #germany #networking #freelance

9

11 Kommentarer

Underestimated service worth the attention, whether you run a react, Vue, Angular, Hugo or whatever SPA or other kind of static website, know you can run it for free in Azure with Azure Static Website. Learn from the best, and enjoy a day packed with SWA goodness

7

"Stop creating architecture diagrams no one understands." In this interview with Björn Helgeson, VP of Engineering at Mindler, he discusses why shared vocabulary should come before technical documentation, and how it enables better business-engineering alignment. Is your architecture documentation building bridges or barriers between teams? Read Björn's interview, featured in the latest edition of Exec Engineering: https://lnkd.in/eh9SYcJh

9

Discover measurements that can inform your ongoing journey of continuous improvement. Checkout this article I wrote for LeadDev - https://lnkd.in/eUcktexe #DORA #metrics #GBGB

28

Thanks for bringing this up Bill Doerrfeld. It's a topic we see highlighted by our larger customers. In some cases, we've seen API teams try to catalog their APIs with an Excel sheet. That never ends well. We're iterating on our internal API catalog with our customers right now, so looking forward to any insights you gather in your article!

4

At the highest level, for me, the development team productivity equation has two components: BANG and BUCK. Improving productivity then starts with either of two questions - how can we increase the value of the software created, and how can we reduce its cost? When you exclude developers from discussions around value (e.g., strategy, customer/user interactions, product design), and then demand greater productivity, you're asking them to do that with one arm tied behind their back. (And then, of course, tie the other arm behind their back by giving them no meaningful autonomy.)

17

4 Kommentarer

So the last reminder that you can catch my Practical Messaging course at GOTO Copenhagen. If you have training budget for 2024 this is your last chance to catch the course this calendar year. The course is structured into two days: * Day One is Messaging Patterns: we cover the fundamentals of asynchronous approaches to integration * Day Two is Conversation Patterns: we look at how to build those exchanges into conversations Along the way we cover topics such as integration styles, reactive programming and reactive architectures. The goal is to leave with you an understanding of the fundamentals of how you use messaging, particularly as a replacement for RPC.

14

1 Kommentar

In this compelling episode of the Mob Mentality Show, we dive deep into the art of Sticky Mob Programming with Lennart Fridén, who brings a wealth of knowledge from his decade-long journey coaching mob programming in Sweden. Whether you're a seasoned mob programmer or new to the concept, this episode is packed with actionable insights and real-world examples that can help you make mobbing a lasting fixture in your team's workflow. https://lnkd.in/g8k_WAjF https://lnkd.in/gv_GWxCy ### Key Discussion Points: **Sticky Mob Programming:** - Lennart’s insights on mob stickiness - Beyond just trying mobbing - Persistent mob habits even without the nudging of a coach  - Mob stickiness challenges and triumphs - Roles: outsider, insider, first follower (AKA eager first dance partner),  - Lessons from "Power of Habit" - Mob as keystone habit leading to a cascade of other beneficial practices - Community and belonging - Dealing with stagnation - Vulnerability and growth **Technical Coaching and Redundancy:** - Embedding coaching and making the coach's role redundant (times two) - Teaching for sustainability - Gradual coach transition examples - Handling eager vs. apathetic first follower (potential future coach) **P.S.** Reach out to Lennart Fridén for guidance on introducing mobbing and ensuring it sticks in your organization. Tune in to discover how to make mob programming a sticky and sustainable practice in your organization! #MobProgramming #EnsembleProgramming #PairProgramming #Coaching #SoftwareDevelopment #Habit #OrganizationChange #ContinuousImprovement #DiffusionOfInnovation #TDD #Learning #Change #ExtremeProgramming #Mentoring #SystemsThinking #StartWithWhy

12

3 Kommentarer

Come and listen to what Dennis has to tell you about how you can transform your apps to perform better and how to give your users a better experience! Your apps on Fastly will just be better!

21