Leonardo Campos

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 Kommentar

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 Kommentar

I'd like to highlight document comparison in #kibana Discover, it can be easily overlooked, it's definitely an advanced feature. Imagine you have several logs with similar URLs, or a SIP message flow of several components that change little part of the message. In such cases this feature will be very helpful, showing you significant differences between selected messages at a single glance. Thanks you so much Davis McPhee for resolving a pretty basic GitHub issue I wrote 2021 with such a great pull request. Davis brought it to the next level, with character, word, line diffing options. This is a feature I wish I had from 2016-2019. Back in those days I spent countless hours analyzing similar signaling messages, mostly SIP. I'll now write an issue pitching for diffing back in time, waiting for Andrea D. providing the mocks, like in the 2021 issue.

23

2 Kommentare

How many of your supposedly internal-only backends are serving critical end-user traffic? Probably more than you think! Most frontend services have many transitive dependencies, and understanding these dependencies becomes increasingly difficult as your system grows in scale and complexity. As a result, it becomes exceptionally tricky to ensure that internal-only backends are fully isolated from end users. Google uses a common infrastructure platform for almost all of its services, internal and external; this provides for a message-passing mechanism common to all of these services. One outcome is that systems engineers can build accurate dependency maps of services; and that we can ensure new services only depend on other services at the same level or higher in the dependency stack. Risky dependencies — in this case, dependencies which place internal-only backends on the critical path for end users — can be a source of major production outages, because the internal-only backends do not generally have necessary reliability or safety guarantees. For example, you might have an externally-visible service that requires high levels of availability and performance, and this system has an indirect dependency on a backend with no availability or performance SLOs. At Google, we found success preventing major and huge outages by clustering services into categories with distinct properties, clear perimeters, and limited blast surfaces. The properties will depend on the guarantees we want to enforce. In this article, we use Google Maps to demonstrate how risky dependencies proliferate in complex systems, and then showcase how clustering Google Maps services into just two categories ("Internal" and "External") can prevent major and huge serving outages. We also outline how OpenTelemetry is used to identify violations of this clustering, which can be fixed before the violations cause a major serving outage. This article is based on a talk at SREcon EMEA, which you can see here: https://lnkd.in/e54b6G6p.

1

I have a couple of side projects running in production. One thing that is a HUGE difference in how I have no hesitation to touch them even after months of not seeing the code (and thus losing context:) Tests. I write them for all the business logic I add / modify. Just did a refactor on a project I wrote 100% of the code of, and have not touched in several months. Confident that my changes are correct, I ran the tests, expecting all of them to pass. Instead, this happened (the below image:) Wow!! My *past self* just prevented my present self from pushing code to production that would have broken this project! Talk about me saving myself! High five to "earlier" me!! I am convinced having these tests are better than anything else that I could have added to these side projects. Coincidentally, side projects I am terrified to touch have no such tests, and I don't feel like understanding the whole codebase (my codebase!) from scratch, again. If you are wondering whether it's worth writing tests: you decide if they are. I know that I don't write these tests for my current self. It's for my future self (or for any other person who will modify the code I wrote, and added descriptive enough tests for)

1.650

107 Kommentare

So, I want to write a bit about why I think the demise of RAG is still far away. During my runs, I often think about how to improve or evolve the systems we already have in production to new architectures. Even with a context window of 100M tokens, we still need a way to select the relevant information. Additionally, we would need to test these models in narrow needle-in-a-haystack evaluations and gather data to confirm that they can reason over such a large context. The most important point is that transformers scale quadratically with the context length. We should also consider how much longer it will take for the user to get a response if we feed 1M tokens to our model. Using something like GPT Caching could help reduce inference time and costs for these types of LLMs. Lastly, I like to compare this to current instances with tens of terabytes of RAM, and we still read and write from disk. We won't need to optimize our RAG pipelines to death but RAG systems would look different just as memory management today looks much different than it did when RAM was only 1GB.

3

Unlocking top-tier software development talent in Germany is a game-changer for any tech-driven business. Our latest blog post dives deep into the best ways to hire dedicated software developers in Germany, offering valuable insights and practical tips. In this comprehensive guide, we cover: 1. The top platforms and agencies for finding skilled developers. 2. Strategies for evaluating and selecting the right talent. 3. Insights into the Germany tech landscape and what makes it a hub for innovation. Whether you're a looking to scale up your business or an established enterprise seeking specialized skills, this guide will help you connect with experienced professionals who can drive your projects forward. Don't miss out on the opportunity to build a development team in one of the world's leading tech markets. Read more: https://lnkd.in/djbV6BXg #hirededicateddevelopers #programming #webdeveloper #software #technology #webdevelopment #softwaredeveloper #softwaredevelopment #development #webdesign #hirededicatedteam #munich #berlin #frankfurt #hamburg #leipzig #germany

6

Yes, it's better for me than for you: I work directly with Hartmut Keil, hence I can ask how they approached LLM benchmarking for working with *German* language. At least you can read the following post from Hartmut about the approach: https://lnkd.in/d_fmgFUZ

8

Yesterday OpenAI introduced their new flagship model - GPT-4o. In a nutshell, these are the most impressive features: It can process real-time audio and video It can talk to us in an empathetic, life-like voice It supports more than 50 languages BCS (Bosnian, Croatian, Serbian) included In the live demos, we could see the conversation with no lag, of which the most impressive use cases for me are: it can view our screen, so it’s a great coding or business assistant it can look through our camera, so it’s a great tuition tool it’s a great language-learning tool and a universal translator super helpful for blind persons or persons with impaired vision It is available through the API, so I’m sure that we’ll soon see amazing new integrations, such as a computer-controlling GPT-4o agent. Apple has been in talks with OpenAI regarding the GPT model’s integration into iOS 18, so we might see that kind of integration on a system level real soon. Exciting times ahead! https://lnkd.in/d88v-R-G

8

⛏️ Many technical teams are facing the web scraping problem. 🤔 Web scraping is not just a technical issue; it's causing a significant drop in productivity for many team members, and we need to address this urgently. That's the reason we launched Scrape.do a couple of years ago: to help Dev teams focus on their core business while we get our hands dirty for them. When I sit back and see hundreds of companies using Scrape.do for web scraping, it shows the trust we have built in this industry. So, if you are still facing web scraping problems, you can start solving them in 30 seconds 😉 #DataScraping #DataAnalytics #WebData #BigData

57

9 Kommentare

One of the more requested examples: how to use the Code Interpreter SDK inside a Next.js app with streaming enabled and using the Vercel's AI SDK

10

Let me ask all the executives at #webagencies and companies who have the final say in #websitedevelopment: Are you frustrated with constant delays 🐌 and escalating 📈 costs❓ Check out pageBody GmbH if you want to speed up🏃‍♀️your #webdevelopment! They have got the right talent and some impressive solutions to make things smoother and faster. Give them a follow❣️

3

RECORDING: Not So Extreme Programming, with Amitai Schleier https://lnkd.in/eQ627KPk Where "#agile" sounds pleasant and inclusive, "#extremeprogramming"... doesn't. But it's a differentiator: teams practicing #xp are seen to move with uncommon agility. The name has other problems, too. For one, XP is about much more than programming. For another, when compared with other ways software still gets developed, XP is much *less* extreme. This talk -- for anyone involved with Agile in any role, at any scale -- will take you through where Extreme Programming came from, where it's going, what it requires, why it remains as relevant as ever, and how to take advantage. RECORDING: Not So Extreme Programming, with Amitai Schleier https://lnkd.in/eQ627KPk #morewithless #agileengineering #organizationaldesign Frans Meuwissen Bastiaan van Hamersveld

11

1 Kommentar

How many of your supposedly internal-only backends are serving critical end-user traffic? Probably more than you think! Most frontend services have many transitive dependencies, and understanding these dependencies becomes increasingly difficult as your system grows in scale and complexity. As a result, it becomes exceptionally tricky to ensure that internal-only backends are fully isolated from end users. Google uses a common infrastructure platform for almost all of its services, internal and external; this provides for a message-passing mechanism common to all of these services. One outcome is that systems engineers can build accurate dependency maps of services; and that we can ensure new services only depend on other services at the same level or higher in the dependency stack. Risky dependencies — in this case, dependencies which place internal-only backends on the critical path for end users — can be a source of major production outages, because the internal-only backends do not generally have necessary reliability or safety guarantees. For example, you might have an externally-visible service that requires high levels of availability and performance, and this system has an indirect dependency on a backend with no availability or performance SLOs. At Google, we found success preventing major and huge outages by clustering services into categories with distinct properties, clear perimeters, and limited blast surfaces. The properties will depend on the guarantees we want to enforce. In this article, we use Google Maps to demonstrate how risky dependencies proliferate in complex systems, and then showcase how clustering Google Maps services into just two categories ("Internal" and "External") can prevent major and huge serving outages. We also outline how OpenTelemetry is used to identify violations of this clustering, which can be fixed before the violations cause a major serving outage. This article is based on a talk by Pierre Theo Klein at SREcon EMEA, which you can see here: https://lnkd.in/e_cyxv_A. Jennifer Steiner Klein collaborated on turning the talk into an article.

39

[YAVA23] 🔸What the CRaC - Superfast JVM startup 🔸Gerrit Grunwald In a world where microservices are more and more a standard architecture for Java based applications running in the cloud, the JVM warmup time can become a limitation. Especially when you look at spinning up new instances of an app as response to changes in load, the warmup time can be a problem. Native images are one solution to solve these problems because their statically ahead of time compiled code simply doesn’t have to warmup and so has short startup time. But even with the shorter startup time and smaller footprint it doesn’t come without a drawback. The overall performance might be slower because of the missing JIT optimisations at runtime. There is a new OpenJDK project called CRaC (Coordinated Restore at Checkpoint) which goal it is to address the JVM warmup problem with a different approach. The idea is to take a snapshot of the running JVM, store it in files and restore the JVM at a later point in time (or even on another machine). This session will give you a short overview of the CRaC project and shows some results from a proof of concept implementation. 🔗 https://lnkd.in/dKqr84Ux

11

📰Introducing Miniflux: A Minimalist Open-Source News Reader🚀 Ever felt overwhelmed by information overload while managing multiple news feeds? Allow me to introduce you to Miniflux - an opinionated, lightweight feed reader that's going to change your life! 😊 Miniflux is written in Go and PostgreSQL, designed for simplicity, speed, and ease-of-use. Its minimalist approach avoids unnecessary features, focusing on the core functionalities of feed management. Why go for Miniflux? - Zero dependencies: Standalone binary ensures hassle-free installation 💻 - Single binary compiled statically without dependency - No ORM or complicated framework: Clean, efficient codebase for developers 🧑‍💻 - Modern Javascript (ES6 and Fetch API): Smooth user experience 🎯 - Extensive documentation: A beginner's best friend 📚 Personally, I've fallen in love with its simplicity. With Miniflux, it's now effortless to browse through different sources and enjoy the news without distraction. I am sure you will find it incredibly useful for your projects too! 💡 Now that you know about Miniflux, I'd love to hear your thoughts on the tool. Have you tried it already? How has it streamlined your workflow? Let's discuss the beauty of minimalism in software development! Feel free to share your feedback or ask questions about Miniflux here 👇 #Miniflux #FeedReaders #OpenSource #GoLang #TechCommunity

5

Thinking Elixir News 202: In this week's edition, we dive into the exciting release of ElixirLS 0.21.0, enhancing the developer experience with new code actions and more efficient dialyzing on the latest OTP. We also discuss José Valim's insightful commentary on Elixir’s upcoming type system, addressing bug-prone comparison operations, and additional advancements in exception handling. Don't miss the unveiling of "Bloom," an opinionated extension to Phoenix core components, alongside Chris McCord's demo of lightning-fast hot code deploys across a global Fly.io cluster. We round off with the legal tussle over the FTC's ruling on non-compete clauses and AWS's S3 billing adjustments that provide relief from unauthorized access charges, and more! #elixir #aws #ftc #devux #developerexperience https://lnkd.in/erkm4F9M

19