Fredrik Stockman

I am interested, where do other people see AI going in the next 10-20 years? 🤔 Initially I think AI will be amazing but I am really scared for the longer term, let me explain: I am really excited for the next five to ten years of AI, I think humans will reach our greatest level of existence. I believe we will see huge levels of economic growth and development. Initially, AI will make businesses more efficient than they could have ever dreamed and the world will prosper. I don't think AI will replace teams but rather supercharge them. That is what we are trying to do with Cloudax with our voice agents and we are seeing this across industries. AI automates monotonous, repetitive processes -> your team can focus on higher value tasks This phase of AI I am really excited by and I believe will truly benefit humanity. However, this tech is moving very fast and eventually, an AGI model will be released or Artificial General Intelligence. This is a model that can understand or perform any task a human can. When a model can do the work of 1000 people, instantaneously and can run 24/7, with minimal expenses, what value does a human employee offer? An entire workforce that is never ill, is a fraction of the price, never complains and produces results instantly. Seriously, what will the value proposition of an entry level employee be? I think this is a very dystopian and scary idea that a large majority of the workforce will lose their value entirely. Everyone says 'yes but that's what people said before the internet or the industrial revolution' but I don't agree. I think AI is the first technology that could have the intelligence to completely replace humans at least within businesses. This poses a huge problem of mass unemployment and uncertainty. It is so exciting the opportunities of AI but I think we have to be very careful. I see it as the largest opportunity and threat that society faces. What do you think, will AI help humans to become more productive or replace them?

12

14 kommentarer

Pair programming is a wonderful tool for creating a cohesive, strong development team. It is more than just a coding approach. Developers can decrease technical debt, build software of higher quality, and foster a culture of ongoing learning and development by cooperating. Strategies I have found useful when starting with peer programming: - Make one developer "Driver" and the other "Navigator", switching responsibilities periodically.  - Prior to beginning, establish clear goals. - Promote polite, honest dialogue wherein developers can exchange thoughts and criticism. Have you tried pair programming in your team? Share your experiences and tips in the comments! #PairProgramming #Agile #SoftwareDevelopment #Collaboration #CodeQuality #ContinuousLearning

79

4 kommentarer

📚 Episode 6 is here! Join Nils and Judith as they continue building the virtual bookshelf with React and SuperBase. We fix the issue with the add book dialogue not closing, handle dialogue state manually with useState, and refactor our code for better organization. Check out our progress and solutions! Watch the episode in the comments! 👇 #code #ux #design #web #React #SuperBase

2

1 kommentar

There's been a lot of talk in the API industry lately about design-first versus code-first. Today Tom Akehurst from WireMock suggests a third option: prototype-first. "An API prototype, unlike a design document or specification, can be used immediately by its consumers. The client code is written, and app features are built early on," says Tom. Upfront design is usually a good idea for API development, but it's not always used in practice. So, could more dynamic prototyping allow the best of both worlds? What do you think? Check out his post on the Nordic APIs blog today for some thoughts about how to mock prototypes and the potential benefits of this approach. https://lnkd.in/eGqGeV7D

11

1 kommentar

When choosing API architectures, you want something that works well with your audience. "Ideally, you want to produce something that fits their needs and works well with their workflows," says Rob Allen, software consultant at Nineteen Feet Ltd. There are many styles to consider these days, from REST to GraphQL, SOAP and XML, RPC-style services, and asynchronous protocols. In his session at Platform Summit 2024, Rob will help make sense of when to use what. Spoiler alert: context matters. I caught up with Rob about the state of API design. He's noticing a resurgence of interest in RESTful HTTP APIs and rising interest in OpenAPI Initiative's new Arazzo specification, among other trends. Check out the interview on Nordic APIs, and be sure to attend The Platform Summit this October for more insights into choosing the best API architecture. https://lnkd.in/e4sGcZnn

16

💡 When you think of Jetpack Compose, what comes to mind first? The UI layer, right? But what if I told you it’s capable of so much more? Today, I discovered something game-changing: you can harness the power of Jetpack Compose within your ViewModel, thanks to a framework called Molecule. Yes, you read that right—Compose isn’t just for UI anymore! Curious how it works? Dive in with me and explore the untapped potential of Jetpack Compose beyond the UI layer. https://lnkd.in/gj997G2P #AndroidDev #JetpackCompose #Molecule #Kotlin #MobileDevelopment

22

3 kommentarer

Now, I am back to being a CTO 🤓 (A.k.a. the best advice I could give to early-stage founders in 2024) The first startup I ever joined, I joined as a CTO. 👋 Shoutout to our SHORTWALK days: Jegor Laptev & Jegor Petsorin. But then, I decided that I thrive in "people roles." So... ➡️ I majored in Social Sciences. ➡️ At EDUKOHT and Taita, I barely touched code. ➡️ In my career as an ~employee~ I almost never coded either. ➡️ I always said, "I code," but "I am not a Software Engineer." But the thing is... You don't have to be a Software Engineer to build a startup. My biggest inspiration is iuliia shnai who learned coding by herself in a couple of weeks and started building micro-products right away. There are so many AI tools that help you build stuff: ➡️ ChatGPT ➡️ Claude ➡️ Cursor ➡️ Copilot ➡️ V0 (They should have named Vercel "Cercel" to stick with C-trend in AI 😂) Anyways... There's no excuse not to build an MVP solution yourself. I am not even touching on no-code and low-code tools such as Make and Retool. What required funding and a team (or at least an experienced CTO) in 2021, requires only a solo founder in 2024. If it wasn't clear yet, I am in my bootstrapping era 💅

40

3 kommentarer

"Founder of future" is Agentic Unifounder. To understand this statement, lets paint future and evaluate possibilities. Imagine you are a solo founder sitting in Reyjavik, Iceland. You are great at one thing: creating, discovering, configuring and orchestrating AI agents. You want to start an ecommerce marketplace in your country but lack access to human talent. Can there be possibility that you can start your ecommerce marketplace with just AI agents? Can there be possibility that you can create a very profitable unicorn with AI agents alone? To extend the thoughts, can this unifounder be selling only to other agents using his/her agents? What are the pro and cons of such a possibility in a country like India?

47

6 kommentarer

Society in general is starting to take bad software seriously. Is your company? Hint: Let's play "bad software practices bingo" and find out! [  ] Like a microwave oven, you let the clock decide if the work's done [  ] The general sentiment is that testing is a vanity metric... [  ] ...So someone other than the developer writes tests... [  ] ...Maybe [  ] You do PI planning and other fika activities at a rate and cost that would bankrupt a small nation [  ] You have several layers of IT roles with inspecific responsibilities [  ] You have a lot of people talking about work, not doing so much of it [  ] Your management does not understand IT, so you have to do "special" (yes, read it in THAT voice) slides for them [  ] You do "quick and dirty" more than once in a lifetime; actually, you do it on a very regular basis [  ] Once per year all teams get to cut down infrastructure spend with 5% because your procurement thinks they can wrench money from AWS' cold, inanimate hands [  ] You estimate stuff to someone who estimates stuff who sometimes nods in blank-eyed agreement [  ] You have no way of knowing if things break before customers/users complain [  ] No one can -actually- say what the hell their software does if [X] leaves [ ] When someone is fired, you get to do/listen to "KT" sessions because -nothing- is documented according to any meaningful practices [  ] No developer has ever spent more than a few hours on quality-enhancing activities like security, observability, or solving known technical debt (go ahead, ask them) [ ] "Design" and "architecture" are things that the team read about in university, and at work these are represented by men in Birkenstocks with oddly specific opinions which can all be safely discarded (like in Rock-Paper-Scissors, PM always wins against Architect) There are so many varieties! What score did you get?

28

2 kommentarer

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 kommentarer

🌟 Revolutionizing Healthcare Communication with Google's Veo Generative AI Video Model 🌟 Exciting news from the world of AI! Google's Veo Generative AI Video Model has the potential to transform how we communicate, educate, and innovate in the healthcare industry. 🎥 What is Veo? Veo is an advanced AI model that generates high-quality 1080p videos from text or image prompts. Its ability to create visually engaging and tailored content opens new doors for communication and training in healthcare. 🏥 How It Can Help Healthcare: - Patient Education: Create clear and engaging explainer videos to help patients understand complex medical conditions, treatments, and procedures. - Training for Professionals: Develop immersive training materials for medical staff, ensuring knowledge retention through interactive visuals. - Awareness Campaigns: Design impactful videos to raise awareness about public health issues, ensuring the message resonates with diverse audiences. - Telemedicine Support: Enhance virtual consultations by integrating customized visual aids, improving patient comprehension and care delivery. The power of AI like Veo in the healthcare industry lies in its ability to simplify communication, bridge knowledge gaps, and drive innovation—all while saving time and resources. This is just the beginning of how AI-driven solutions are shaping the future of healthcare. Excited to see how tools like Veo will continue to make a difference in improving patient care and advancing the industry. What are your thoughts on leveraging generative AI for healthcare? Let’s connect and discuss! #HealthcareInnovation #AI #GenerativeAI #GoogleCloud #VeoAI #PatientCare #HealthTech

9

We help companies to build great software to automate their business. ✨ Recently, we understood that we can use our knowledge not only in software development but in other niches as well. ✨Now we can help you with the coolest ads your product deserves to stand out. ✨ Previously, to shoot an add like this cost you a fortune. ✨ Now we do it on a fraction of a dollar. Ask me how I can help you. // #AI #aiautomation #aiads #aimarketing #aigeneratedvideo #aigeneratedads

1

I don't care if AI automates me out of my job. It is no secret that there is a mindset in the air that many roles humans currently perform will be outsourced to AI. And in several areas of several industries, this has kind of already happened so I am not here to tell people their fears are invalid. In the last year for example, every time I have gone to Starbucks I have had discussions with my wife about how I've never had to have interactions with a human and nobody just walks up to the counter and orders. At half of the grocery stores I go to now, I don't need to interact with a cashier when purchasing food. Given this reality, many people see the obstacles from these events, that there will probably be fewer cashiers at grocery stores or fewer humans necessary to run a Starbucks location. So that could displace these people from their jobs. Even larger tech companies like Amazon and Google are obviously and publicly using AI to do as much as possible that humans don't necessarily need to do. Some fears are overblown but that's to discuss for another post. Instead what I want to bring up today is yes companies are using AI to make their companies more efficient and require hiring fewer humans. But a select few of you reading this might also see the flip side of the coin to that reality about how this can benefit us as individual people, job seekers, employees and businesspeople. We don't have to just sit back and moan that companies are reaping all these benefits and we're powerless. Why? The reality is, we have more power than we ever have had before. I bet a lot of people reading this have wanted to start a business or create a product or an elaborate project, but have decided not to because of obstacles in technical skills or other things of the sort. But now with all of these AI tools available to streamline a lot of things, sure companies benefit but now it's also easier for each of us to create something we want to with AI's help. And I'm not just here making some crazy claim that people can create sources of income for themselves using AI, I've actually done this in my own business. One of my main uses for AI is helping me create step by step walkthroughs of problems for clients more quickly. And does the fact that some of these walkthroughs take me 1-2 minutes to create stop my clients from paying? Absolutely not, they value results they get from these documents, not the time I spent creating them. What is the takeaway here? You can decide for yourself, but my main takeaway is that people that see opportunities in their lives will always win over people that only see obstacles. For people that only see obstacles, how are they handling the AI boom? What benefit is there to simply worrying without taking action? If people would like one or more follow up posts talking about concrete ways you can see the opportunities in these AI tools rather than the obstacles, please add a comment!

24

36 kommentarer

"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

How I got offers to be the CTO in a South Korean startup, a co-founder with an engineering manager at Google in SF, and a lead developer in a Nordic project (unrelated to my previous posts about job offers). In early 2023, a few months after the release of ChatGPT-3, "chat with your PDF document(s)" apps were popping up everywhere. While these functionalities are now common, they weren't back then. I found an open-source code for a simple demo of this kind of app. I'm not sure what got into me, but I forked (cloned) it, and decided to add a lot more features to it and completely rework it. In particular, I made it a full-stack application: you could upload multiple documents, create/delete multiple chat windows and use specific documents within them, have context-aware conversations in respect to the chat history, and more. I put it together in 1-2 weeks, and released it as an open-source project on GitHub. Posted it on Twitter (1st tweet, 0 followers). It received ~40k views and +700 stars on GitHub. Everything else I made before that point got 0. I then started getting messages from people. 1/ An engineering manager at Google in SF wanted to be an equal-part co-founder in an AI project. We had a few calls, some at midnight, but it eventually dissolved because the guy's vision for the app was the kind that would've needed a team of full-time developers and a few months. Ambition is great, but this was a fever dream (I would've been the solo dev). 2/ Someone from South Korea reached out, offering me to be the CTO in their new startup. No salary, just equity. The startup? "Your AI platform for everything." Again, the limit of what I can do is pretty high, but I'm not (too) delusional. Other than me, there were two other guys. They had me sign an NDA, of course. Needles to say, I didn't join. Their homepage is the same as it was a year ago. 3/ Two people working in software engineering (although not developers) from the Nordics reached out. I thought what they envisioned was a little out of scope, but nevertheless doable. They asked for my hourly rate, and I gave them what is probably equivalent to senior engineers at large companies in Slovakia, but still probably lower than mid-level devs in Nordic countries. They said 'Sure, no problem', then ghosted me lol. I guess it was a problem after all. Sorry, purchasing power parity is great, but only for the products I buy, not for the salaries I get. And with all that, I thought to myself: if I can put together something in 1-2 weeks and have it potentially change the course of my life, then the last couple of years I've spent learning to code have not been in vain. This project didn't change my life, but I became more optimistic. I realized that a totally different life and future might be one side project away. That's why I launched the last project, and why I'll keep launching more. Sooner or later, we'll get there. Not a shred of doubt about that in my mind.

27

1 kommentar

Dangerous change in Android 15 📢 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.

938

34 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

Is it finally time to say goodbye to ugly Objective-C wrappers for Kotlin shared code in our Kotlin Multiplatform apps? 🚀 Even though we started working with KMP less than a year ago, I still believe we are in the group of early adopters of this technology. Until now, we have used KMP to build two different apps which have roughly 80 downloads per day 📈 With that being said, during this year, one of the main issues of our iOS team had with debugging the compiled shared code was that KMP is currently generating Objective-C headers from Kotlin code 🤔 We are aware that Google will release Swift interoperability during this year, but I always thought to myself, there has to be a better way to do it. And, totally by accident, I found it today 💡 So apparently, there is a framework: https://skie.touchlab.co/, which can be used in KMP projects to generate Swift code based on generated Objective-C headers 🤯 I still didn’t try it out, but I plan on doing it in the upcoming week. Community developed frameworks rock 🤘🏻

27

3 kommentarer