Saif Bechan

Key takeaways from Maarten Balliauw’s talk at #dotnetdays: Microservices for building an IDE – The innards of JetBrains Rider 💡 💭 We learned about the magic that powers the most innovative IDEs: JetBrains Rider. We looked at how and why we have built (and open sourced) a reactive protocol, and how the IDE uses a “microservices” architecture to communicate with the debugger, Roslyn, a WPF renderer and even other tools like Unity3D. Key notes from the talk: ✔️ JetBrains IDEs are built on the IntelliJ IDEA platform (JVM), ReSharper is .NET. In Rider, these two platforms need to work together! We built an open-source protocol for that. ✔️ Both the frontend (IntelliJ IDEA) and backend (ReSharper) are IDEs. How do you merge functionality from both, given they are built on top of a different runtime (JVM and .NET). ✔️ The benefit of having a protocol like we use in JetBrains Rider is that we can easily spawn more helper processes for functionality, without bloating the main IDE processes. #dotnetdays2024 #marteenbaillaw #techconference #keyideas #dotnet #microservices #jetbrains #IDE #reshaper #JVM

10

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!

27

1 comentario

[YAVA23] 🔸Chopping the monolith 🔸Nicolas Fränkel 🇺🇦🇬🇪 Microservices are ubiquitous. However, most companies that implement microservices do not reap their full benefits - at best. At worst, it’s an epic failure. There are reasons for microservices: independent deployment of business capabilities. However, the unspoken assumption is that you need to deploy all capabilities all the time. My experience has shown me that it’s plain wrong. Some capabilities need frequent deployment, while some are much more stable. In “the past”, we used Rule Engines to allow updating business rules without deployment. While it solved the problem, this approach had issues. Between introducing a Rule Engine and migrating your complete system to microservices, I believe that there’s a middle path, and that this path is Function-as-a-Service. In this talk, I’ll detail every point I’ve made above, and show how one can use Serverless to pragmatically design a system that allows deploying as often as you need. 🔗https://lnkd.in/gVzRqB9c

10

✍🏽 We have a new article on our blog! This time, José Alejandro Sulbarán Armas, lead front-end developer at Leniolabs_, shares his expertise as a technical interviewer, focusing on the key soft-skills that will attract the interviewer’s attention. 🔗👇🏽 Read the full article: https://lnkd.in/d2_D5Cw4 #technicalinterview #interviewtips #softskills

7

This is the last sale I will do for my #Angular Change Detection ebook. The content in there is still valid 🚀 And I promise it will help you understand Angular way better. It's an absolute steal 24 - 18 = 6 € excl VAT (limited)🤑 Not up to date with signals and experimental zoneless. Angular 16 This book is special for me because it is the first piece of paid content I created for simplified courses and I'm glad I sold hundreds of copies. For anyone who has supported me in buying that book, thank you so much. It was a real motivator. https://lnkd.in/ecgVs6mg Next focus: Building/Maintaining huge #Angular codebases course.

21

10 comentarios

👉We have been chatting to a couple of new clients in Germany this week, about using freelance Developers/Engineers outside of Germany (Nearshore), the same questions pop up; ✔How do we know if they are good or not? ✔How much can we save? ✔How quickly can they start? 👀Like anything, there is pros and cons to everywhere, but we have built a network of Freelance Nearshore Engineers who have been rigorously vetted with technical expertise guaranteed, that could save you a 50% reduction on your current freelance rates. If you are interested to understand more about this option and how this could help your business. 🚨Feel free to book a call in my Calendly and let’s see if we can help - https://lnkd.in/eygXyhaz

8

3 comentarios

Are you looking to level up your Docker networking skills? In this extensive video, you'll gain the knowledge to choose the perfect Docker network for your specific use cases. We'll delve deep into various network types such as bridge, host, overlay, macvlan, and more, providing a comprehensive overview of their benefits. By the end of the video, you'll have a solid understanding of each network type's strengths and when to use them, empowering you to enhance the performance and security of your Docker containers to meet your unique requirements. https://lnkd.in/dr7ExUHN Giving back to the open source community - A sloopstash initiative. #docker #devops #container #network

4

We just finalized the agenda for our next meetup: Spring 2024 Edition of Site Reliability Engineering Munich group takes place on April 25th. We appreciate jambit hosting us this time in their office next to S-Bahn Hirschgarten. #SRE #Simplicity #Rust #SREcon Agenda: 6:30 pm Get together with food and drinks 7:00 pm jambit welcomes you to SREmuc 7:10 pm Talk 1: Simplicity in the Source (Markus Teich, Google) 7:40 pm Talk 2: Enough Go, what about Rust? (Mario Ortiz Manero, Lyft) 8:10pm Talk 3: Recap SREcon Americas (Ingo Averdunk, IBM) 8:40 pm Networking + Drinks 9:00 pm Leave happy and inspired :) Speakers & Abstract: Talk 1: Title: Simplicity in the Source (Markus Teich, Google) Markus has been an SRE and software engineer at Google for close to 7 years. In his open source endeavours he learned a few things about running open source software and how code simplicity can help with long term maintenance. As an SRE at Google Markus has looked through many different types of code bases across various languages. In this talk he'll share some of his observations on how code can be easier to understand and how that can help with incident management and maintenance. Talk 2: Enough Go, what about Rust? (Mario Ortiz Manero, Lyft) Working on the open source project Tremor - an event processing system - Mario has gathered some good knowledge about using rust to write production systems that can scale. He is going to give us valuable insights when Rust is a great language to use and where it can possibly win over the hearts of dedicated Gophers. Talk 3: Recap SREcon Americas (Ingo Averdunk, IBM) Following the theme from previous years, Ingo will recap SREcon 2024 Americas. Just like speed dating, Ingo will attempt to collapse 3 conference days into a 30-minute session. The objective is to provide food for thought and to encourage listening to the playback of interesting sessions. More about the event on Meetup https://lnkd.in/ePwwsz-a

15

1 comentario

Still buzzing from #kcdczsk2024 we are taking our #kubernetes optimization and governance platform to #KCDBarcelona24 hosted by DevBcn 🎉 Do not miss Ivan Yurochko from #perfectscale talk on "Navigating and Optimizing Karpenter - Avoiding Common Pitfalls"

9

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.

22

3 comentarios

Are you looking to enhance your Spring Boot application by integrating multiple authentication providers seamlessly? In modern web applications, particularly those using microservices, it's crucial to manage various identity providers efficiently. In blog post on Medium, our colleague Sebastijan Kaplar delves into the importance of using multiple authentication providers and how it can significantly improve the modularity and scalability of your system. Whether you're dealing with internal or external endpoints, learn how to configure your application to handle tokens issued by different providers like AWS Cognito and Azure AD. Discover practical steps and insights on setting up a robust authentication framework that adapts to your growing business needs. Curious to know more? Dive into the full blog on Medium! https://lnkd.in/dUv7uaGe

1

Can I help senior developers? 🧐 Yes! In fact, my course was developed after watching thousands of senior developers make the same mistakes, over and over again, in how they present themselves via LinkedIn, résumé or during the interview. Telling senior developers that they are not great at something is a HARD sell! 🤭 The developers that did listen, at first, were juniors and those trying to break into tech. The truth is that the problems are the same. Whe those on my course land jobs, they often tell me that they endeavour to return when they need my help for the next career jump. I respond by stating that if they have listened ... they won't need me 🤯😲 What REALLY blows their minds is when I remind them that if they do come back for further help .... it's FREE. I will help you forever 🙇 #seniorsoftwareengineer #seniordeveloper #career #developer

17

Big news for Box API developers: Versioning is coming! We're excited to announce the upcoming rollout of versioning for the Box API. This means more control, stability, and flexibility for you when building your apps. What does this mean for you? - Stability you can rely on: No more sleepless nights worrying about API changes breaking your applications. - Freedom to choose: Select the API version that perfectly aligns with your development needs. - Smooth sailing upgrades: Effortlessly transition to newer versions whenever you're ready. Curious about the specifics and how it works? Check out the details in our article. Here's the exciting part: Your input shapes the future of Box API versioning! ️ We value your feedback. Share your thoughts, suggestions, and questions in the comments below. We're all ears! #BoxAPI #Versioning #DeveloperLove #DeveloperCommunity

7

"(Please note the key is generated by a Java Applet that loads on the screen, if the Java applet has not loaded, please ensure that the latest version of Java Runtime Environment is installed on the computer being used)" Really? This payment processor still requires you to run a Java applet in your browser?

6

3 comentarios

Hey folks, I need some advice. -- What are the top 3-5 things you do when making an API? Does your team have a standard way of writing APIs? Do you do api design reviews? Thanks for your help 🚢 #ApiDesign #SoftwareEngineering

172

59 comentarios

Just a few more hours before our webinar "Empowering Java Applications with NoSQL: A Hands-On Workshop" starts! ⏰ Join us as we discuss with Otavio Santana how NoSQL databases can advance your Java applications: https://lnkd.in/enCHHytD #NoSQL #JavaDeveloper #JavaApplications #FreeWorkshop #TechWebinar

13