Francesco Napoletano

Nature is healing: https://lnkd.in/dztKzJw4

3

If you want LinkedIn impressions without putting in any hard work, I’ve got some tips for you: - Say TDD sucks. - Make fun of a silly sales pitch. - Share a meme. - Tell a joke. - Post a picture of your test suite (green ticks) or say you never have time to write tests. - Say PHP doesn’t suck. - Say Clean Code exists. Welcome to the jungle. Watch it bring you to your n-n-n-n-n-n-n-n knees, knees.

54

21 commenti

Software Engineers, this one is for you! After a record year of growth and profitability at Prima, we are expanding our teams and I’m looking for software engineers who want to take their careers to the next level. Here are the key bits of information: 👉We are a remote first company offering employment in the UK, Italy, Spain, and Germany 👉We have a strong commitment to flexible working. I know that being a mum of two how important that is! 🤗 👉The connection between people is our cultural cornerstone. The company offers fully funded team off-sites and you will have the opportunity to explore places with your team. As an example, we have been to Milan, Lake Como, Rome, Madrid, Barcelona, Bologna to name a few. 👉By the way, we were using AI before it became a modern tech obsession. So, if AI/Machine Learning is an area you want to grow in, now is your chance. You would be a great fit, if you’re someone who: 🤩 Cares about the systems they build. It’s not just another job. It is your passion 🤩 Is aware of emerging technological and architectural trends 🤩 Wants to learn and grow 🤩 Is a strong communicator with focus on providing a fantastic service to our customers We have a varied technology stack including Rust, Python, Elixir, React, AWS (and many more) But we look for people who are willing to learn and adapt. So, you could be from any background. Just so you know, my background is C++, C#, Angular, React, Azure. So, if you’re willing to learn different technologies, we will support you 🚀 PLUS: you’ll get to work with me, and I’m awesome 🤣🤣 Jokes aside, if you want to give yourself a new role in the new year, drop me a message here and I’ll respond. Tag and share with your connections too if you feel like they might be a good fit. *Here’s a cute cat photo to add to the post Christmas silliness 😻

68

6 commenti

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

Here are the slides for my GopherCon.EU talk: How to Win Frames and Influence Pointers https://lnkd.in/d7byRQfu #gopherconEU #golang

72

4 commenti

No developer likes an API that breaks. Thankfully, there are ways you can test for breaking changes in APIs, using methods like specification-based diffing with tools like oasdiff, contract testing, functional testing, performance monitoring, following developer-centric communications, and other tactics. I recently wrote up a summary of various methods and tools for testing APIs for breaking changes on the Treblle blog. Give it a read here: https://lnkd.in/eh2RDNDP #api #apis #apitesting #breakingchanges

11

its not a secret that i hate headless CMSs they give you hardcoded-hell codebases where every non trivial change to a page is a new engineering ticket, which no one enjoys (devs or non devs) component composition is a much better path forward, and it gets more obvious each day, especially with the latest advancements in LLMs: https://lnkd.in/gis5xF53

209

18 commenti

Our APIs no longer redirects from http to https. At DinnerBooking we have a lot of APIs so restaurants can get all kind of data about their bookings. We used to redirect any http request automatically over to https for security, but we have now stopped doing that. Why you may ask. I was reading this article about "Your API Shouldn't Redirect HTTP to HTTPS" from https://lnkd.in/dvD3MYuh Here they suggest to apply to the Fail-fast Principle, which makes a lot of sense. So now our APIs responses with a 403 error saying "The DinnerBooking API is only accessible over HTTPS"

17

Simplify your database management with #Prisma #ORM. Learn more at onlycoders.net for a comprehensive guide.

1

My latest article for the Box Developer Blog has landed. Using the new Box TypeScript SDK I show how to easily create an exportable folder report with shared links to all the documents https://lnkd.in/ejA-qQKh

21

1 commento

𝐋𝐞𝐭 𝐦𝐞 (𝐫𝐞)𝐢𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐞 𝐦𝐲𝐬𝐞𝐥𝐟! I've seen an influx of followers as of late, and passed 5k followers on here, which I still have no clue what to do with. Nevertheless, let me (re)introduce myself! I'm a Norwegian based in Amsterdam. - A Software Engineering Manager with one foot planted in AI/ML/Applied Science, and one foot firmly planted in Software Engineering. Which includes System Design, Distributed Systems, and lots of Computer Science that fall outside the scope of AI/ML. - Because even if Computer Science and Software Engineering has fallen in the shadow of AI lately, the most impressive Deep Learning models in the world are nothing without the Software Engineering that goes into serving it to customers in an efficient and enjoyable way. You wouldn't be able to appreciate Netflix's awesome recommender algorithm if videos were stopping all the time because the system couldn't handle millions of concurrent users. AI 🤝 Engineering Aside from being driven to solve problems by applying AI and engineering best practices, I'm 𝐏𝐀𝐒𝐒𝐈𝐎𝐍𝐀𝐓𝐄 about being an awesome leader to the teams and engineers I manage. Which is easier said than done because people problems are 𝐚𝐫𝐠𝐮𝐚𝐛𝐥𝐲 𝐡𝐚𝐫𝐝𝐞𝐫 𝐭𝐨 𝐬𝐨𝐥𝐯𝐞 𝐭𝐡𝐚𝐧 𝐦𝐚𝐧𝐲 𝐭𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐩𝐫𝐨𝐛𝐥𝐞𝐦𝐬. If you don't agree, then I bet you 1 brunost that you're a smug IC, maybe a Tech Lead, who has never actually had the people management responsibilities of a large team 😉 I love it, though. 𝐍𝐢𝐜𝐞 𝐭𝐨 𝐦𝐞𝐞𝐭 𝐲𝐨𝐮! - Who are 𝘠𝘖𝘜??! And what would you like me to post about?

118

28 commenti

Think building integrations in-house is worth the hassle? Think again. In our latest post, we uncover the hidden costs many teams miss, or discover too late: 😵 Developer resource drain: A production-ready integration often takes months, not weeks, to get right. ⏳ Lower product velocity: A slower time to market can impact customer conversion and satisfaction + lower dev productivity. 🔄 Ongoing maintenance costs: The more APIs you integrate with, the more complex things get—welcome to maintenance hell. We cover these challenges in further detail in the post to help you decide: is in-house worth it? Link in comment 🔗

14

1 commento

Incorrect Generalizations with Amitai: einfach = simple vielfach = complicated nullfach = impossible

9

1 commento

The most common complaint I hear about serverless is that it "is difficult to test". And this is where I most strongly disagree. In fact, I will try to prove that serverless actually is much easier to test and debug than the more common solution of using a container or a local server. Why do I say this? Simple: a serverless application is built out of isolated functions. Each function is a component, that receives an input and an output, and the services it uses are injected as arguments.   If anyone remembers the basics of the Spring Framework (which is an Inversion of Control, a testing framework at its core), the concept is the same, just at the infrastructure level. With this structure it is extremely easy to write tests: all you need to do is to pass arguments, and, if you are using external services, provide mocks for them. Serverless also makes it easy to write integration tests because the deployment is fast and can be integrated into the test code itself. However, in my experience. people who are used to building with containers are upset by this experience and complain that they "can't debug it". They expect to be able to start the server (which they cannot do with functions) and tweak with the application by interacting with it, often manually playing with the UI. The truth is that they are not used to writing tests at all . They don't do that, period. So they start the whole thing, interact with it often at the UI level and attach a debugger to find out what is wrong.  Of course this is a bad practice because you do not get a repeatable test suite, and what is worse, you have to test the whole thing instead of unit tests. Unit testing an entire server is much more harder than testing functions. So the truth is: is not that serverless is hard to test, it is that you usually do not write tests for your code at all.

21

3 commenti

☕️ Here's an entry from the Small Batches library: "Focus on Arrows". From Release It! (2018): A new architect will focus on the boxes; an experienced one is more interested in the arrows. Comment below on this applies to your daily work.

2

✍🏻 New post on the zeroheight blog: As a follow-up to the livestream with Garrison Snelling, I share the benefits of adding code examples in your #DesignSystem documentation and how to do it with StackBlitz: https://lnkd.in/eTywhvSU

10