Sebastian Bille

Knowledge Sharing: Day 22 Breaking change if you are planning to upgrade your compileSDK to Android 15 or higher 📢 If you use Kotlin's list.removeFirst() or list.removeLast() extensions in your Android app, then, after bumping compileSdk to 35, your app will crash at runtime on older Android versions. #android15 #android #behaviour #development Kaara

34

3 Comments

Our next Comsysto blog post is out! 🎉 Big thanks to our colleague Filip Kisić for creating this interesting piece on SwiftUI best practices! Blog post features: 🌟 Practical examples 🌟 Clean Architecture principles 🌟 Ready to use code snippets 🔗 Get the full blog post here: https://lnkd.in/d52pwqMZ #iOSDevelopment #SwiftUI #TechBlog #CleanArchitecture

10

Stripe, GitHub, and Microsoft Graph API are examples of companies doing API versioning right. Here's an overview of what to consider to retain happy API customers from version to version.

2

𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐜𝐢𝐞𝐬 𝐯𝐬 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 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!!!

30

9 Comments

Developers don't like breaking changes. It's worse if these changes weren't communicated in the first place! Here is a roundup of techniques to consider to make API versioning painless.

5

New blog post! https://lnkd.in/dKRJuRdH Today I decided to write about pair and mob programming - and how I think there is an overly focus on _coding_. I see pair and mob programming more as coming together to _collaborate_. That's independent of whether that involves things like brainstorming, writing documentation, debugging, reviewing code or...coding. Any thoughts or reflections?

8

2 Comments

Thank you Sigurd Meldgaard for the boost 🙌🏻 3 weeks ago Ive raised a suggestion request for pub.dev on LinkedIn and on GitHub too, luckily some of the Flutter Dev and Google community members liked my idea and within a week they implemented the idea on https://pub.dev website ✨ ⭐ What's new on pub.dev: Now you can copy the latest version of any of your package from https://pub.dev website *directly from the listing* 😋 You dont have to dive into the detail page 'just to copy' the latest version ⚡ Also thanks for the approval István Soós 🌟 and thanks Lukas Klingsbo for the Github issue reminder 🦺 🔗 Heres the reference of my previous post: https://lnkd.in/em9vHCaW 🔗 Github Issue reference: https://lnkd.in/eUcj5grc #flutter #google #dart #flutterdev #flutterdeveloper #opensource #pubdev #linkedin #github #flutterdeveloper #fluttercommunity #support #suggestion #enhancement #developer #hybriddeveloper #userexperience

58

4 Comments

We're live with Groq! Check out this quick demo of how to use Groq with Freeplay, for when ultra low latency inference matters.

2

1 Comment

Embedded developers with niche skills are like gold dust. If you find one, don’t hesitate... hire them quickly. I see over and over that these specialists are often snapped up by companies that understand their value. That means your hiring process needs to be not just fast, but also enticing. Competitive salaries, interesting projects, and a clear path for career growth are essential if you want to attract and retain this top talent. Speed and flexibility in hiring can make all the difference 🙏 The companies that adapt their recruitment strategies to move quickly are the ones that will come out on top.

3

Traditionally, API management platforms combined different features (like gateways, analytics, and developer portals) into one big package. But this approach has limitations - it isn't very flexible or scalable. Shift toward unbundling API management allows organizations to pick and choose the specific components they need. This way, they can create customized solutions that fit their requirements. However, this approach also comes with challenges, such as dealing with complex integrations and managing different vendors. Feel free to explore the full article for more in-depth insights! https://lnkd.in/eag23q3s #APIDesign #APILifecycle #APIManagement #APIs

5

3 Comments

How do you write code for complex asynchronous operations that is simple and intuitive? Magnus Mikkelsen, Software Developer at Kamstrup, shared his experiences on this exact subject with other IT professionals at our Morning Meetup last Tuesday. 🧠💡 Using examples in C# and Rx.Net, Magnus started with well-known collection types and then delved into how Rx.Net works and what it can do. Thanks to Magnus for the inspiring presentation and all who joined us that morning. Hopefully, we will meet again at our next Morning Meetup in the New Year! 🤝✨

4

Improve how your #Vaadin app handles long backend actions. From showing progress indicators to async processes, Matti Tahvonen shares the best ways to keep users engaged. Check out the demo! 🔗 Dive in: https://bit.ly/4dwwcnx

12

"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

In this piece, we introduce you to the SOAP API format, compare it to other protocols like REST, and demonstrate how to work with SOAP APIs within Python.

2

GPT-powered software agents are heralded as the next step beyond chatbots, but have only partly lived up to the hype so far. 👿 Currently agents tend to be fail due to pile-up of errors in subprocesses. For example a five-step process for an agent with individual error rates of, say, 5% lead to overall error of 26,4%. That is without taking into account that all you do to make this better, tends to make the agents *fragile*. That is, they become prone to failing due to model updates or data drift for instance. Improving sub-processes at some point always involved human-annotated data, which doesn't really scale - up till now. 😯 In this very recent interesting paper by google deepmind, they seem to have found a way to potentially improve agentic workflows *without the need for human annotation*. If this approach works beyond the context they have tried this approach in the paper (math problems), this makes agents much more feasible then they are now! 😀 Incidentally the key idea is to provide much more detailed feedback to the model beyond a simple 'works' or 'doesn't work'. I find this type of feedback tends to work better for humans too :). #AI #AIImpact #Agents

10

Good take. It is common to confuse "how simple and straightforward a system/algo is" with good code/design/architecture, which is a blatant confusion. It carries, indeed, some inner pleasure to see clear implementations in the whole system, but sometimes they come at a cost since it also means that the team is either not aware of the underlying volatilities of the business or they don't care. Both can be detrimental in the long run.

5