Daniel Patricio Sorichetti

I wanted to share an interesting article I read yesterday and really recommend everyone in my network - CTOs, Heads of Engineering and Software Developers - to really understand the benefits of #Kotlin in server-side development if: 1. You haven't had a play around with the language before 2. Are considering modifying your existing tech stack and looking at more modern and performant options Compared to #Java, the Kotlin programming language developed fantastically by JetBrains removes a lot of the 'nitty gritty' work you would otherwise have to work through and requires WAAAAY fewer lines of code than doing the same work in Java! Not to mention, the incredible features around #NullSafety and #Coroutines. Have a read to understand more on the positives of using Kotlin in the JVM languages as well as the benefits of migrating your tech stack to this optimised language. #Tech #SoftwareDevelopment #Coding

3

Leaving in a few hours for #warsaw to speak at #JSPoland soon🔥 (and the lineup of the speakers is incredible) I'm excited to be speaking among other amazing speakers in the #javascript world sharing their experiences and expertise. I will be talking about a topic closed to my heart 💟! Which includes my struggles, hurdles, and how I overcame them. A journey from someone who stopped reading books, to someone who now loves reading but not only that, became an author himself. (you know what the fun part is?) I never thought I'd give this talk. Or even about sharing my journey. But that's what I say always. It is not about the end-goal; it is about the process. I stopped focusing on the results YEARS ago. And focused on the "now". And as a by-product, I have stories to tell. I have experience to share. (but what's the best learning out of this experience?) Everyone has stories to share. And experience to spread among others. It does however require time, efforts, and most importantly, "reflection" to explore, think, and refine our stories that we'd love to share with others. And that's exactly what I'm going to do in November and December at SIX different conferences. The idea is to be authentic with your work, and the people around, not to shy away from putting in the hard work, and availing any opportunity thrown your way. If you're around any of these cities around these dates, let's meet over a coffee or something. • 6 - 7 Nov - Warsaw, Poland • 9 Nov - Nuremberg, Germany • 13 Nov - Malmo, Sweden • 16 Nov - Venezia, Italy • 6 - 7 Dec - Lahore, Pakistan • 8 - Dec - Karachi, Pakistan

67

6 Comments

This summer searching for work goes slower than previous. Despite it is the same CV at the same target salary (and +1 year of experience). Yesterday I've seen this funny notification on the job-site: I applied or responded to 100 positions since the beginning of the August - and "my chances are growing" - oh, thanks :) Actually it looks either the job market is under some influence, or the general flow turned to worse - I had written down all interviews I had already, of them only 3 tech interviews/screenings (and one online-testing), one managerial interview - and 12 interviews with various HRs. It looks like the market is really flooded by low-level recruiting agents these days and communication between candidate and employers is disordered by this extra layer. #hiring #hr #recruiting #job

4

👀 Did someone say open governance should have an open roadmap? 🎉 https://lnkd.in/eBwdGEu4 🎉 Our first roadmap has been approved by the TSC and formally published! Early in our project, it was important to set our community up for success: copying HashiCorp Vault (for better or worse) was not a viable strategy to build a sustainable community and especially a fork. There simply aren't enough hours in the day to continually do clean-room reimplementations of proprietary features... We'd always be playing catch up. Thus we opted to differentiate ourselves in a key way: listen to the community. Many of the features on our roadmap are things that the community has publicly asked for on the upstream issue tracker and been ignored, time and time again. Paginated lists, because the UI hangs on KV or PKI mounts with lots of entries. Transactional storage, because networking isn't always reliable or timeouts may happen and changes should be rolled back, not left in a random state. PKCS#11 support in OSS editions because, frankly, it is 2024 and strong security is a basic necessity for everyone when running a secrets manager. Improving the mount table limit, because there are times when ~14k secrets engines just aren't enough. The list goes on. Our roadmap seeks to prioritize a few key areas where we think we can make improvements: in safety, in scalability, and in building a community around OpenBao. So check out our roadmap! If there's something that interests you and you wish to contribute, we're happy to work with you!

17

A first block of 4 weeks of continuous coding in Spain is over. Some findings: 💡 There are many excellent software libraries, but their usability is usually limited if you have a specific application in mind. Don't be afraid to build something from scratch instead of trying to force an existing solution into yours. 💡 Reductionist approaches to developing a new technology require a lot of time and thought in the beginning, but pay off in the long run in terms of scalability and speed. You just have to bite the bullet first, the fun comes later. 💡 The negative impact of aging on concentration or learning ability is non-existent, so age can no longer be used as an excuse for making mental efforts :) 💡 Golden cages blunt creativity, curiosity and wonder. I am already looking forward to my second coding camp next month. Now off to Belgium to build further on the work done here, beyond the current hype of artificial intelligence. #innovation #finance

9

I've just contributed 156 examples to the Spanish FineWeb 2 dataset! https://lnkd.in/dbPwcuSH If you're contributing to the FineWeb 2 Sprint, check the "Share Progress" button at the bottom-right of your annotation screen and share your contribution with the world!

27

2 Comments

Even though the article from 🌀 Luca Rossi is mainly about "How Engineering Management is Changing", personally I see the strongest take away that "engineers are more and more full-stack these days." and "full-stack developer doesn’t stop at coding". I absolutely agree that thanks to more powerful programming languages and tools, future of development is in multi-proficiency. As a developer embrace it and become Full Scope Developer or simply be left behind 🤷‍♂️ Just imagine: - no big teams - no syns meetings between FE - BE - AI - Devs - no waiting when other side is done just an idea and one Full Scope Developer who makes it happen. This is what REAL agile means ... no pre-planned scheduled ceremonies. #impact #agile #small #team #talent #simple #smart #softwareengineer #softwaredeveloper https://lnkd.in/eneeKxbS

13

9 Comments

CTOs, you need to make a choice 📍Local Teams: - Direct oversight - 3-6 months to hire - Limited talent pool - Easy communication - €120K+ per developer 📍Nearshore Teams (Europe): - Same culture - Same time zone - Some travel needed  - €50-70K per developer - 2-4 weeks to hire - Large talent pool 📍Offshore Teams: - Lowest rates (€30-40K) - Huge talent pool - Major time zone gaps - Cultural misalignment - High turnover - Inconsistent quality Which one makes most sense❓❓ Here’s my 2 cents: ➡️Nearshore teams win. ➡️By A MILE. It just hits the sweet spot: 🟢Time-zone alignment 🟢Cost efficiency 🟢Speed to hire 🟢Quality work 🟢Cultural fit After helping 80+ teams scale. I know it for sure.. The future is distributed. And big companies are starting to realize this.

45

20 Comments

We are not going to hire juniors in 2025 While everyone is building strategies and preparing to 2025, I want to remind you why we don't work with juniors and how it benefits our results. The thing is - our clients come to us expecting the best. Juniors are great for some teams, but not for ours. We don’t have the time or room to train beginners. And the most important - we don't have any desire to mess up our clients projects. Some companies take pride in growing talent from scratch. We don’t. Our focus is results, not potential. I'd rater choose someone who is ready for challenges, who can take responsibility and deliver unbelievably great results. Do you hire juniors to build them up, or do you stick to experienced professionals? #TeamBuilding #TechTalent #Leadership #Developers #2025IT

4

2 Comments

💡 [TIP] How do you handle unexpected news as an Engineering Manager? In day-to-day work, you and your teams sometimes receive unexpected news that can shake the team's motivation. As Engineering Manager, how are you handling this? Here is how I’m approaching these situations in case it helps you reinforce your own mindset: 1️⃣ Understand this reality: companies evolve. One day, your best teammate might leave. Another day, you might decide to move on. And on another day, the company might make changes. That’s just how it works. 2️⃣ So, I ask myself this question: What opportunities can my teams and I find in this situation? 3️⃣ If you're following step number 3️⃣ , I can ensure you that you'll find at least 1 opportunity to grow. 4️⃣ Communicate this to your teams and remain open to deeply listening to their thoughts and proposals. 5️⃣ Create your own plan to seize the opportunity. The ideal world doesn’t exist. And perhaps it doesn’t because “ideal” means something different to everyone. 🙂 This may sound obvious, but when we receive unexpected news, we tend to ask ourselves why and try to understand it, investing energy in something that probably isn’t up to us. This leads to frustration and exhaustion when it’s unnecessary. I choose to keep fighting to protect my #energy and #motivation. What about you? More content related to engineering management at https://lnkd.in/dNePvQJV #team #growth #engineeringmanager #manager #productivity

10

🌟 Reflecting on My Journey with Haptiq: Growth and Learnings Over the Last 2 Years 🚀 Over the past two years at Haptiq, I’ve had the incredible opportunity to grow both technically and professionally. Here’s a look at some of the key areas I've focused on: 🔹 Java Backend Development – I’ve worked extensively with Spring Boot, JPA, and Hibernate to build robust backend services, ensuring scalability and performance in complex systems. 🔹 Upgrading Java & Spring Boot – Keeping up with the latest advancements, I’ve successfully upgraded Java and Spring Boot versions, ensuring my projects stay current with the latest features, security updates, and performance improvements. 🔹 Dockerization – I’ve embraced Docker to containerize applications, enhancing the portability and scalability of services across different environments while simplifying deployment processes. 🔹 Mentoring Juniors & Code Reviews – One of the most rewarding parts of my role has been mentoring junior developers. Conducting code reviews, sharing best practices, and helping them grow has been fulfilling and has reinforced the importance of clean, maintainable code. 🔹 Upgrading Legacy Systems – I’ve had the chance to work on upgrading legacy codebases to the latest technologies, improving performance, security, and maintainability while reducing technical debt. 🔹 Agile Collaboration with the Team – Working in an Agile environment, I’ve collaborated closely with cross-functional teams, contributing to sprint planning, daily stand-ups, and retrospectives. This collaborative approach has enhanced my problem-solving abilities and fostered effective communication across teams. 🔹 Training and Skilling with Udemy Business – At Haptiq, I’ve been fortunate to access Udemy Business for ongoing learning and skill development. This platform has allowed me to stay up-to-date with the latest trends in technology, from backend to frontend development, ensuring continuous personal and professional growth. 🔹 Learning ReactJS – I’ve also expanded my skill set by diving into ReactJS, building modern, dynamic, and responsive frontend interfaces to create seamless user experiences. 🔹 AI Exposure Training – Recently, I’ve started gaining exposure to AI technologies, learning about machine learning models, neural networks, and the role of AI in shaping the future of tech. It’s an exciting new area I’m passionate about, and I’m eager to explore further. Special Thanks to Amol Dhanpalwar, Sunny Kachhia , Hrishikesh Raverkar⚡ A huge thank you to Haptiq (previously Webonise) for providing such a supportive and collaborative work culture. The opportunities for growth, learning, and continuous improvement have been invaluable, and I’m excited for what’s to come! #Java #SpringBoot #Docker #Mentorship #BackendDevelopment #CodeReviews #TechLeadership #LegacyUpgrades #Agile #Collaboration #UdemyBusiness #LearningAndDevelopment #ReactJS #AI #SoftwareDevelopment #ContinuousLearning

22

Just got my copy of Asynchronous Programming with C++ from Javier Reguera Salgado and Juan Antonio Rufes ! I believe performance is an essential feature of any software. I used Asio alot over the years and cmake-re is full of it, looking forward how we can optimize it further with this knowledge! #cpp #asio #cplusplus

25

1 Comment

67% of EU companies struggle to find developers Most of them pay 30% more than necessary And they take at least 3x longer to hire Not. Good. For. Business...  In 17 years in tech staffing, I learned one thing: 👉If you can’t find talent, you’re probably searching the wrong places.    This is what numbers say. ❌ Companies spend 90 days looking for local developers  ✅ Our partners get qualified developers in just 2-3 weeks.    ❌ EU companies pay €85,000/year for senior developers  ✅ Our global talent with SAME skills costs €45,000/year    ❌ The average annual retention is most companies is 70%  ✅94% of our devs remain with their teams for 1+ year    MORE IMPORTANTLY  ==================    👉98% of our clients hit all their technical milestones on time     👉....and within budget     (We measure this using monthly project reviews) In short, Stop limiting yourself to local markets. With 30,000+ pre-vetted developers globally, Your next star developer is out there. 👉Follow me for more business insights 👉Drop a comment below with one thing you don't like about hiring new teams.

64

32 Comments

Headless, boneless, skinless & lifeless UI I love these new definitions!!! What about you? Link on the first comment 👍 💬 Like and share your thoughts in the comments. ♻️ Share this post to spread the message. 🇪🇸☕ If you’re ever in Madrid, let’s grab a coffee!

9

3 Comments

Engineering is not religion. The people I distrust the most are the ones who try to sell anything as binary: GOOD vs BAD in engineering. And first and foremost, in #software #architecture. By fighting the "pro" church, you become a member of the "against" church, like below. Same force, just opposite direction. Don't fall for "against" church, but don't fall for "pro" church either. #microservices, #microfrontends, #eventsourcing, whatever! Remember, architecture is about tradeoffs. And there's no room for tradeoffs in religion.

29

15 Comments

Recently I finished reading the amazing https://lnkd.in/dyAVZc8P by Gergely Orosz, and there was a one idea that hit me the hardest. In the chapter about job switching, there is a statement that more senior roles require more tenure. The reasoning is pretty reasonable: more senior IC folks are supposed to work on complex and impactful things. One definitely needs some time to build connections, learn the domains and pain points before doing that. A person, who switches senior+ jobs often looks a bit suspicious, because it’s almost impossible to achieve anything worthy in a year or two. Can you agree? Well, I totally agree with that, but there is one thing, that I realized. If you are a senior+ individual contributor, and your tenure is already more than a year, but you are STILL not working on something impactful, that’s probably a trouble. After a couple of years you will be in the same situation: you have the fancy title and tenure, but no achievements, which looks like a red flag as well. Tenure matters, but you need to make sure to make something cool during that time.

20

1 Comment