Simo Haakana

It's been years since Java 8 was released, but let's revisit this change in Java. it’s crucial to understand the memory management within the JVM to optimize our applications and prevent memory-related issues. Two key concepts in this area are PermGen Space and Metaspace. PermGen Space: Permanent Generation (PermGen) was used in versions up to Java 7 to store metadata about the classes, methods, and other reflective data. It had a fixed size, which often led to OutOfMemoryError: PermGen space if the application loaded too many classes or methods, especially in large enterprise applications or those using frameworks that dynamically generate classes (like Hibernate or Spring). Transition to Metaspace: With the release of Java 8, PermGen was replaced by Metaspace. Metaspace uses native memory (outside of the heap) for class metadata, offering more flexibility and alleviating the fixed-size constraint of PermGen. The size of Metaspace can grow dynamically, reducing the likelihood of running out of memory, though it still can be controlled via the -XX:MaxMetaspaceSize flag. Advantages of Metaspace: Dynamic Sizing: Metaspace can expand as needed, which helps avoid the OutOfMemoryError that was common with PermGen. Improved Performance: Class metadata management in Metaspace is more efficient, leading to better performance of Java applications. Best Practices: Monitor Metaspace Usage: Use tools like jconsole, jvisualvm, or JMX to monitor and profile Metaspace usage. Set Limits: Use -XX:MetaspaceSize and -XX:MaxMetaspaceSize to control the initial and maximum size of Metaspace, ensuring your application doesn’t consume all available native memory. Optimize Class Loading: Review your application’s class loading and unloading patterns. Avoid excessive class loading, especially in web applications with frequent redeployments. Web : https://lnkd.in/g8GnqxGF #Java #Programming #JVM #MemoryManagement #JavaDeveloper #TechTalk

9

💥 Six months have passed since the extensive rollout of GitHub Copilot to Volvo Cars' developer community. "We expected significant efficiency gains of approximately 20%, but tasks like unit testing have surpassed expectations and seen gains of up to 40%", says product developer Sabina Edenlund, who sits on Volvo Cars' Gen AI committee. GitHub Copilot assists developers with testing, explaining, and generating code, and can support the advanced ‘autocompletion’ of coding. ➡ Learn more how Volvo Cars benefited from GitHub Ccpilot https://lnkd.in/ee9f6Y7s #microsoftazure #GitHubCopilot #microsoftadvocate

6

What should you consider when using Amazon RDS with AWS Lambda? Check out a new blog article by our Arttu Pekkarinen!

5

Principles on a wiki page... not a good strategy for organizational change. If you are part of an Architecture Modernization Enabling Team (or similar), creating documentation is a tiny part of your responsibilities. You need to get out there and spend time with teams, help them to understand and adopt principles, translate principles to their context, repeat the message until it sticks, get feedback and improve yourself... and just think about the whole developer experience. If you are looking for inspiration then look here: Truls Jørgensen & Audun Fauchald Strand. They gave an exceptional case study on this topic at QCon London 2022 (or some other time during the twilight pandemic years). https://lnkd.in/dtEmKGGi One thing I love about working at PayFit France is being part of a motivated staff engineering community that is always trying to improve in this area. #architectureModernization

59

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

https://lnkd.in/dxqQa5kn Just read a fantastic article by Christian Heilmann 👀 that I couldn't help but share. In this article, Christian passionately defends the role of frontend developers and highlights the critical importance of specialized expertise in web development. Christian perfectly captures the essence of what it means to be a frontend developer today. We're not just writing HTML, CSS, and JavaScript. We're crafting the very interfaces that define user experiences across all devices and browsers. His experiences with major companies like Yahoo, Bing, and Microsoft, as well as his work on browsers like Firefox and Edge, underscore the significance of having dedicated frontend professionals. One standout point was the common misconception that frontend work is somehow less "real" than backend or full-stack development. Christian dismantles this myth by highlighting the deep expertise required in performance optimization, cross-browser compatibility, and accessibility. I highly recommend reading this article, especially in an era where the push for full-stack generalists can sometimes overshadow the need for dedicated frontend expertise. It’s a powerful reminder that having specialized skills is crucial and that investing in experts can save time, money, and headaches down the line. #TechInsights #FrontendDev #LGUW #LGUW14dayschallenge

7

4 kommenttia

Six months have passed since the extensive rollout of GitHub Copilot to Volvo Cars' developer community.​ "We expected significant efficiency gains of approximately 20%, but tasks like unit testing have surpassed expectations and seen gains of up to 40%", says product developer Sabina Edenlund, who sits on Volvo Cars' Gen AI committee.​ GitHub Copilot assists developers with testing, explaining, and generating code, and can support the advanced ‘autocompletion’ of coding. ​ ​ ➡ Learn more how Volvo Cars benefited from GitHub Copilot: https://lnkd.in/dPfGruTq #GitHubCopilot #DeveloperProductivity #MicrosoftAzure

16

2 kommenttia

This one is out of the topic of software development and engineering stuff that I usually talk about. First, the reason for a ship logo can be explained: It's useless here. Useless things suck in software development and writing code. I have been sceptical about it many times and posted stuff on optimisation while criticising stupidly written code and software. That's kind opposite on the business side of things. Let me clear this out I am not a strategy marketing person or an experienced startup guy, but a consumer and I have experience of watching companies steal attention and make people buy things that have way less probability of usage than the straightforward ones. I remember those days when Siri was new in the market and only iPhones managed to get the voice commands to work. It was I think 10 years ago when people I know were rushing to buy iPhones. When I asked them about what's great about it, most of the time I didn't hear about "it has those cool processors" or "smooth and gorgeous display", which was expected from Apple. Rather, most of them were interested in "Oh it has Siri, it supports voice commands" and "that the high-end technology, I can talk with my phone, OMG". 10 years after that, I have had a Macbook for 2 years now and haven't even thought of using Siri anytime. For me, and most of the people back in the day, Siri was kind of "useless" in my terms but was a solid hit for getting the product into the market. Okay, get this: Nobody told me that the iPhone 5 has an "Apple A6 1.6GHz" processor or a crystal clear display, mostly at the top of the margin. But somewhere or the other, I was shown Siri. I remember my close relative showing me Siri and calling a person with it, but I never saw him using it to make a call time. He would literally wash his hands if he was cooking and would pick up the call with his hands. To be clear, I am not undermining anything. Siri was ahead of its time and an important innovation, but looking at its usage by most of the crowd, it was mostly useless to a general crowd of users. The same goes with the Rabbit r1. It's a cool concept but seems to be failing in the current market and I don't find any use case from my side (even Marquee Brownlee can't find it). But it spread like wildfire, a new concept with a small device as an assistant. I hope they make it right in the future, but for now, it remains useless and popular at the same time. And that's the moral of the story: A few useless things tend to attract more attention than those which are expected from the brand, which can be used to turn it positively if done correctly. You can get these insights for free in my Newsletter, directly in your inbox with no effort from your side: https://lnkd.in/gDVBY9hC

5

kubectl auth can-i get kubestronaut ☸ ⭕ Now I am certified from Cloud Native Computing Foundation (CNCF) and The Linux Foundation as Kubernetes Administrator (CKA) This couldn't be done without the one and only Mumshad Mannambeth, and of course Kim Wüstkamp with Killer Shell. #kubernetes #cka #kubectl #linux #devops #orchestration #container #linuxFoundation #CNCF #systemengineering #cluster #kubernetescluster

122

32 kommenttia

DevOps is a way of working. Every company does it differently.

9

Developers use boolean logic operators on a daily basis. While some priorities were always clear to me, others I was not sure about. This is the reason why I wrote this slide deck. Also please remember: We are programmers, not mathematicians. Always use as many lines and comments as needed to write better understandable code! 🔔 Your weekly tech boost 🔔 Discover new tips and insights on NodeJS and TypeScript every week. Expect hands-on tutorials, expert advice, and the latest industry trends. Don’t miss out – follow me for your weekly dose of tech wisdom! 🧙‍♂️ #javascript #typescript #logicoperators #dev #junordev

5

"If it's boring - automate it. Release notes are boring" Whenever you ship a new release you probably need a release note, a report listing the new version number, fixed issues, new features… Why write all that manually? By building up your traces and recording your trails as you work, you can pull all this information out of your backend automatically. You’ve written your last release note. From here on out it’s release notes as code. --- This card is marked #intermediate in the #build area in the Continuous Delivery Metric Model Who writes your release notes? I've been in projects where developers and tech writes would spend weeks on updating documentation and release notes on the back of each release. But of course if you only have four releases per year then... No - wait! Maybe that's WHY you only have four releases per year!

26

2 kommenttia

DORA's yearly "State of DevOps Report" is out and it should consider and apply some kind of "inflation reduction act" for page count. 120 pages, yes, 120 pages. Okay, there are a lot of pictures (like in good old uni times), but still 120 pages. The only significant reduction in page count was in 2020 when they switched to a different format. About the report: yes high-performing teams are doing better than low-performing teams. And AI will make everything better #DORA #State-of-DevOps #humour

16

2 kommenttia

One of the questions I get asked the most is: “Hey Aleksa, where can I find good articles about NavigationStack vs UINavigationController” 📱 While I talk about that topic here a lot, I still didn’t time to write a blog post about it, so I always go and research are there some existing posts about this topic. And I have a feeling that there aren’t enough posts which tackle this topic out there 😅 That made me think why is that the case 🤔 I believe it’s just simply because people didn’t have time to use NavigationStack in large scale apps just yet and see how it performs in comparison to UINavigationController. We just to need to wait a little bit more ⌛️ When it comes to my personal opinion, I was team NavigationStack, then after I tried it out on a slightly bigger iOS project, I went back to team UINavigationController+Coordinators 😂 One thing that might change my mind in the near future is this library: https://lnkd.in/eFH6hyPp which Catalin recommended to me. I have already tried their example project and it looks promising so far🤘🏻

33

6 kommenttia

Too many 'software engineers' today are glorified code monkeys. Harsh? Maybe. True? Absolutely. - 90% can't explain how their code runs in production - 95% have never touched a database outside their ORM - 99% think 'infrastructure' is someone else's problem News flash: AI is coming for your job, one-trick pony. The future belongs to the curious. The explorers. The 'how does this whole thing work' nerds. Why? Because they'll be conducting the AI symphony while you're still tuning your one-string banjo. Here’s 4 signs you're on the endangered list: 1. Your knowledge of DevOps doesn’t go beyond merging your own PR 2. You've never SSH'd into a server (it's not a disease, I promise) 3. Your debugging process is 'console.log' and pray 4. You think scaling means adding more if-else statements Embrace curiosity. Break things. Ask 'why' until your team wants to mute you on Slack. Because in the AI future, the curious engineer doesn't just survive. They thrive. P.S. If this post made you angry, you might be a code monkey. Don't worry, there's still time to evolve. 🐒→🧑‍💻

147

46 kommenttia

There are many things to consider when implementing Serverless applications with relational database engines. Read from Arttu's blog how to take benefit from technologies and frameworks such as Lambda Layers, SQLAlchemy, RDS Proxy & FastAPI in building resilient and high-performance Serverless applications 💪 #aws #serverless #lambda #performance #resiliency #rds #fastapi #heromakers

5

1 kommentti

Arguably, for code navigation instead of left/right moving to the previous/next character, the default should be previous/next word instead. I have happily used it for years (with an alternative alt+ijkl layout). How is that not a thing in every talk about developer productivity?

1