Davide Pollicino

I'll be talking about building future-proof React applications on the 30th of May in Bucharest. Everyone needs to have a set of principles they follow so they don't have to think about every problem from scratch. I'll tell you how I've been building React applications for the last 8 years. What works. What doesn't. What to focus on to make sure you don't have to rewrite your application every year. Because programming is about solving problems. But engineering is about maintaining those solutions over time.

100

3 komentáře

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

Interested in optimizing your development workflow? Our latest blog post explores the ins and outs of leveraging Dev Mode with Payara Micro Maven plugin, guiding you step by step in the creation, running and development of a Payara Micro Maven project in IntelliJ IDEA. Learn how to use key features, such as auto-deploy and live reload to streamline your coding process: https://lnkd.in/eR_VG8hn #JavaDevelopment #Java #JakartaEE #DevMode

7

The guide to kubectl I never had. From the content: What kind of engineer are you? 🤔 Can somebody guess by just looking at you? More than likely not. Would that somebody be able to tell by looking at your keyboard instead? Might be a bit easier now. ⌨️...[read more] Follow #techbeatly @techbeatly gmsocial, tbsocial

1

Why I Broke Up with NavigationView for NavigationStack 💔 Me to NavigationView: "It’s not you, it’s me... Actually, no, it is you. You’re just too... outdated." 😬 💡 NavigationStack slides in: "I heard you like clean, predictable navigation. Let’s make your app drama-free." 🎉 Now, with NavigationStack, navigating between views is so smooth, it feels like I’m swiping on a dating app. No weird reloads, no confusion—just one view at a time. 📱 My app: "Finally, I can stop seeing my views fight each other for attention like it's the Hunger Games." 👀 PSA: If you’re still using NavigationView, it’s like using dial-up internet at a fiber-optic party. Time to upgrade before your code ghosts you! 😂 https://lnkd.in/err3bdJQ #iOSGlowUp #NavigationStackForever #NoMoreViewDrama #SwipeRightOnBetterNavigation

3

The async advantage: how I built remote engineering teams that actually work. I was always working with engineering teams in Slovenia, Hungary, Croatia, and Belarus AND Switzerland. My secret sauce for remote and hybrid communication? When working with hybrid teams, especially with such diverse teams, it’s tempting to think tools like Slack and Zoom will solve everything, but the truth is, it’s a balancing act between asynchronous and synchronous communication. It may sound obvious, but get it wrong and your team's productivity could collapse. Let me explain... Asynchronous tools like email, project management boards or pre-recorded videos let your team work at their own pace, no matter what time zone they're in. It is a completely new situation when you have to deal with people who have different schedules and are trying to cope with the unpredictability of life. On the other hand, synchronisation tools - those infamous video calls, Teams and Slack messages or WhatsApp pings - demand instant attention and real-time participation. They can be useful, but overdo it and you'll kill your focus faster than you can say “zoom fatigue”. Here's the catch: Europe is facing a serious talent shortage. We're talking about a shortfall of 500k developers, with a particularly painful gap in AI, cybersecurity and cloud computing roles. In addition, your team wants to work in a hybrid environment. For me, having remote talent has always been the default, and the key to success is a balanced communication. I’ve seen projects fail not because the engineers weren’t talented, but because communication fell apart. Remote success hinges on understanding when to let people focus and when to jump into real-time discussions. Too many sync meetings kill productivity, but too little face-time can make collaboration feel like shouting into the void. My biggest learning? It’s all about balance: leveraging async for deep work and sync for crucial alignment. The moment you find that sweet spot, your team thrives. #RemoteLeadership #AsyncWork #Nearshoring #HybridTeams #SoftwareEngineering

19

6 komentářů

Hey, everyone on LinkedIn! How is it going? Today, I want to showcase Webserv, the most recent project I've completed at 42 Wolfsburg. Wait, but what is "Webserv"? Webserv is a project in the 42 Wolfsburg core curriculum focused on creating your own HTTP server. It is capable of initializing infinite (well, infinite as far as your system allows) servers as well as handling a great number of clients simultaneously. The technology behind it allows handling all the I/O operations asynchronously,  ensuring that no single request can block the entire server. Moreover, it is capable of handling static and dynamic content, allowing the creation of interactive and dynamic web applications. Anyway, there's a lot I can say about this project, but, as they say, "it's better to see it once than to hear about it a hundred times". Feel free to check out the link to the project on my Github and onward to the next accomplishment! #42Wolfsburg #Programming #CodingJourney

20

Over the past few months I’ve written an extensive tutorial on how to build software applications with Node.js and React. I’m sorry to tell you that this experience didn’t teach me anything about B2B sales, though. But hopefully, it’s still useful for some people out there. From the introduction: The approach of this tutorial is to teach its readers how to build a fully working software application from zero to production. This means two things: 1. You are not required to have done any kind of software development before getting started with this tutorial. It will introduce and explain everything that is needed to build applications in full detail, assuming no prior knowledge or experience. This is the “from zero” part. 2. Building on the foundational knowledge it teaches in the first half, the tutorial will then, step by step, guide you through the process of building a real, full-fledged, and completely working software application, again explaining every detail along the way, and shows how to “deploy” that application — that is, how to make that application available on the Internet for anyone to use. This is the “to production” part. Speaking of B2B sales: I’m afraid you cannot buy this tutorial. That’s because I’m making it available for free, as a series of posts on my blog. The first three parts are already published: https://lnkd.in/e2XCYm3p https://lnkd.in/eW7wUc_d https://lnkd.in/eAU6kgH9 No, you do not need to sign up to my newsletter to get access to the tutorial. That’s mainly because I don’t have a newsletter. Also, no need to follow me (although admittedly, it might help to get you notified whenever I’m publishing a new chapter). Furthermore, please don’t be disappointed if clicking on the tutorial links won’t present you with a cookie banner. That’s because my blog doesn’t use any cookies. No, not even those from Google Analytics, as I’m not using that either. This means I will have no idea how many people will read the tutorial — which makes sense because let’s face it, who is going to consume this kind of long-form, deep-dive technical content nowadays anyway. And in text-only form, of all things! Should you nevertheless decide to dive into the text, expect to learn how to program using JavaScript and TypeScript, how to use these languages to build rock-stable backend applications with Node.js as well as elegant frontend applications with React and Redux, and finally, how publish a complete and integrated software solution on Amazon AWS. Ok, that’s it. If you want to access the bonus chapters, simply subscribe to… — just kidding. There are no bonus chapters. Everything you need to learn to build useful software products is right in the… normal chapters, I guess? Happy reading!

30

1 komentář

Needing tips for technical interviews? 🎢 Technical interviews can be quite a rollercoaster, but you can dial down the stress with some preparation. 🎢 Kuznietsova Viktoriia and Marko Saaresto share valuable tips and tricks in Rakettitiede's blog, based on the previous Mimmit koodaa webinar. Hop on the blog to read more! #MimmitKoodaa

9

2 komentáře

The number of full-remote positions for software engineers is decreasing. There are many reasons for this, but here is one data point: remote management can be harder. This observation comes from Sabin Roman, the first engineering manager at Linear, which remains a full-remote startup. Sabin was an EM at Uber before this, so has plenty to compare. We went into comparing notes on what it's like to work at Linear vs at Uber in the full podcast episode. Watch it there: YouTube: https://lnkd.in/eZNgKHrs Other platforms and transcript: https://lnkd.in/ew89pM4a Data about the number of full-remote positions dropping in this The Pragmatic Engineer deepdive: https://lnkd.in/dzWeeFUK

195

22 komentářů

Kotlin 2.0 here it is! We were ready for it as were our books. 📚 The whole Kotlin book series by Marcin Moskala is updated to the new version of Kotlin 2.0 ⭐ Grab a copy and elevate your Kotlin skills today! https://kt.academy/book

3

In what world would anyone use microservices, when there is a thing called monolithic architecture. Yesterday I attended AWS Cloud Day in Prague, where they had a coffee stand where you could order coffee using their app built using microservices. From what I understood, it is a proof of concept, but I can’t see how it’s a proof of concept and not a proof, that you can indroduce a lot of useless complexity you add to a project, when you decide to use microservices. During breaks between the lectures, I built an app, which achieves pretty much all things their app does, only without the phone number verification. It took me in total of 20 minutes to build the backend and 40 minutes to create decent frontend using HTMX and Tailwind CSS. I simply think that 90% of projects would eliminate a lot of useless complexity, if they built their apps woth monolith architecture. https://lnkd.in/eX6P3HNW https://grugbrain.dev/

6

Many of us are working on exciting projects but only few succeed. During my attendance to two European Ruby conferences in June, I had the opportunity to ask top Ruby developers this crucial question: why do software projects fail? These are some great insights they shared on common pitfalls, unexpected challenges, and lessons learned from project failures . Watch my full video on my YouTube channel for more in-depth insights and discussions: youtube.com/@tillcarlos

6

In the past year, I've worked with Uberto Barbini to write an article about the benefits of using #functionalprogramming in web applications. It was a pleasant endeavour, and I learned a lot. Among the key points: Maintaining an internal mutable state is challenging. We change the context for subsequent interactions each time we interact with a program. Object Oriented Programming (OOP) and Functional Programming (FP) try to provide solutions for handling the software’s maintainability and complexity. OOP encapsulates away the complexity, while FP focuses on data and its transformations. Functional programming concepts improve predictability, promote code reuse, and manage side effects—the FP’s emphasis on immutability and composability results in more robust and maintainable systems. FP improves web applications by treating them as data transformation pipelines. It encourages using pure functions to transform input data into output data, leading to transparent data flow, easier testing, and more predictable behaviour. Kotlin seamlessly blends object-oriented and functional programming, allowing for the gradual adoption of functional concepts in existing codebases. This results in more expressive, concise, and safer code that can improve maintainability and reduce errors. You can read the whole article on InfoQ, and if you want even more than that - you can read Uberto's book, which also contains points related to #DDD and how to properly build software.

8

2 komentáře

A lot of users (you might be one of them...) head to W3Schools.com with a specific thing in mind - like wanting a job in tech, and needing those specific skills to land it 🧑‍💻👩‍💻. Then, when getting their hands dirty in developing the skills, they'd have a load of questions, like ‘should I learn this developer language?’ or ‘do I need this qualification?’ They really needed guiding through this journey. So, when W3schools wanted to introduce a new, personalised app to help users here, W3schools Pathfinder was born. And we helped them build it. Read the full story here ➡️ https://lnkd.in/dQBPAuqS #nordcloudbytes #genAI #generativeAI #applicationdevelopment

35

1 komentář

🤓 It's not hard to hire a senior developer You're just not offering them what they want. I posted a survey in a Slack group with devs, asking this question: "Would you as a senior developer be open to change jobs NOW if you can work 100% remotely?" (Btw, many of them are social and will come to the office more often. They just want true flexibility and quality of life. And to be fair, they want to do what they love, which is coding, with the minimum amount of interruptions.) Although the dataset is small, the results are interesting. 💸 38 % are willing to take a lower salary if they can work remotely ❓ 17 % would join a company that has some financial uncertainty if they can work remotely 😑 41 % would take a job with a less exciting role, product and techstack if they can work remotely This is an incredible opportunity to hire some seriously great engineers. Especially if you: — Can't pay the highest salaries — Don't build spaceships or AI agents — Are located in a small town or rural area Are there tradeoffs and challenges with (some) remote team members? Of course. But I just can't understand why more companies are not willing to take some risk here. You might regret this when the market turns upwards again. 🕺🏻

105

43 komentářů

🚀Exciting Insights from the 2024 ZK Community Survey!🚀 Our latest survey reveals fascinating trends among ZK developers! From IntelliJ becoming the top IDE to Maven leading as the preferred build tool, explore how your peers are shaping the tech landscape. Stay informed and join the conversation: https://lnkd.in/gxr9W9J8 Thank you for your continued support and insights! 💡 ✨ #ZKSurvey2024 #DevTrends #IntelliJ #Maven #JUnit #JavaEE #JakartaEE #Baeldung #StackOverflow #AIIntegration #ZKFramework

4

☕ The Coffee-Driven Code Review Manifesto: A Sleep-Deprived Guide to Excellence [Everyone talks about clean code, but let's be honest - most of our best reviews happen after that third espresso shot] 🌅 6 AM: First Commit Code looking pristine Tests all green Documentation spotless Reality: Haven't written a single line yet ☀️ 9 AM: The Morning Stand-up Revelation "Wait, did I just promise to deliver this by EOD?" Frantically opens IDE Types while drinking coffee Spills coffee on keyboard Git commits anyway 🌮 12 PM: The Lunchtime Code Review PR Comment: "Interesting choice of variable names. Is 'pizzaTime' really the best name for a payment processing function?"  Me: "I was hungry when I wrote that..." 🌙 5 PM: The Final Push git commit -m "Fixed everything (hopefully)"  git push origin please-work  git prayer --recursive 📊 Our Revolutionary Metrics: Bugs Found vs Coffees Consumed (1:1 ratio) Time Spent Reviewing vs Time Spent Making Memes About Code Number of "LGTM" Comments That Actually Meant "I Trust You” 🎯 Pro Tips for Sleep-Deprived Reviews: If the code works on the fifth try, it's probably production-ready Comments like "Magic. Don't Touch." are perfectly acceptable documentation If you can't explain your code, blame it on the keyboard 🤔 The Real Code Review Checklist: Does it work? No one knows why it works But it works Ship it! 💭 Question for fellow night owls: What's your record for most consecutive hours staring at a PR before realizing you were looking at the wrong branch? #CodingLife #TechHumor #SoftwareEngineering #DeveloperLife #CodeReview #CoffeeDriver Development #TechMemes

2