Josue (Josh) Abreu

📱Porting Software to ARM64 Architecture: Everything You Need to Know📲

10

The recording for Will Sewell's talk from the latest Observability Engineering Community London tech meetup is here! A few takeaways: ⇥ Dependency management is a significant challenge in microservices. ⇥ Centralized migrations help maintain consistency across services. ⇥ No downtime is crucial during migrations for operational stability. ⇥ Using a Monzo tracing SDK allows for controlled rollouts. ⇥ A monorepo structure simplifies service updates and consistency. ⇥ Automated rollback checks ensure safe deployments. ⇥ Config services enable rapid changes across multiple services. ⇥ Gradual ramp-up of new features minimizes risk during migrations. ⇥ Strong ownership models enhance accountability and service management.

29

1 Comment

The 2024 StackOverflow survey is out, and for the 8th year in a row, Clojure has ranked near the podium in the Top Paying Technologies category—often occupying rank 1. I don't talk much about why I choose to use a weird Lisp—mostly because nobody cares—but the results speak for themselves. If you can hold your nose long enough to learn something very different, you'll find yourself in a high-productivity environment that features: 🔥 Hot code reloading 🦆 Dynamic typing ♻️ Best-in-class garbage collection 📂 Highly performant immutable data structures 📚 Access to the entire JVM's ecosystem of libraries 🧩 Cross-platform compilation to JavaScript 🧠 An unbelievably smart and humble community Sure, you'll pay a high mental price to learn the language, but as a reward, employers will pay a high price for *you*.

72

47 Comments

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

We just raised $22m to make Kubernetes work for your developers and fix app deployment to the cloud. This new funding was led by Slater Stich at Bain Capital Ventures and Sandeep Bhadra at Vertex Ventures. Frederik Brix and I started Northflank with one mission: to make deploying complex workloads as straightforward as possible for developers. Somewhere along the way, it feels like the industry shifted focus from building great products to building the factories that make them. To bring that focus back, we've made significant product engineering investments that have laid the foundation for our growth. By centering on the needs of developers, we've introduced features like Bring Your Own Cloud (BYOC), enterprise-grade capabilities, preview environments and GitOps support. Leveraging Kubernetes as an operating system and providing the right abstractions, we've empowered developers to deploy complex workloads effortlessly, be it micro-services, stateful databases or jobs across six clouds, 100 regions and 300 Availability Zones. Today, Northflank supports tens of thousands of developers in production, handling over 1.3 million container deployments every month. With this new backing, we’re gearing up to scale our platform even further to help enterprises run complex workloads around the world and support customers like Writer, Sentry, and many more. I’m incredibly grateful to our earliest supporters—Steve Jang at Kindred Ventures, Luke Byrne at pebblebed, Patrick Murphy & Alex Mackenzie at Tapestry VC—who believed in us from the beginning. And I’m excited to welcome new partners Amanda Huang & Slater at Bain, Salil Deshpande at Uncorrelated Ventures, and more, to our journey with this Series A. I'm also thrilled to announce that Chase Roberts is joining Northflank as our new COO! He’s coming to us from Vertex, who led our Seed round, and brings a wealth of operating experience from his time at Box and Segment. I used to joke with Fred about how we could convince Chase to join the team full-time—his energy and drive are contagious. When Chase saw our vision to simplify cloud infrastructure, he couldn’t stop thinking about it; having him on board in this role feels like a perfect fit. Thank you to our new angels for believing in what we're building: Scott Johnston CEO at Docker, Inc, David Cramer Co-Founder at Sentry, Oskari Saarenmaa Co-Founder at Aiven. Ian Livingstone Kris Beevers, Jerry Ting, jeff settle, Steve Manuel and more! And most importantly, a huge thank you to our customers who trust us with their most important workloads. We're just getting started!

338

72 Comments

At the risk of starting a flame war: what's the benefit of using Gradle over Maven? Almost every Gradle project I've downloaded fails to start without tinkering, whereas Maven projects generally just work. Gradle also doesn't seem to support the latest Java. What am I missing?

27

11 Comments

Follow up to our "Tiered Storage Won't Fix Kafka" blog post. This one explains all the benefits of WarpStream's Zero Disk Architecture beyond just reducing costs! https://lnkd.in/epjCSVMv

71

1 Comment

Excellent blog by Kitson Kelly on the performance differences between various JavaScript and TypeScript runtimes, including Deno, Bun, Node.js, Deno Deploy, and Cloudflare Workers. - It details the benchmarking methodology and presents results on latency and request-handling capabilities under different loads. - The analysis shows that while Bun and Deno offer superior performance locally, Cloudflare Workers handle edge computing tasks more efficiently at scale. Link: https://lnkd.in/gTzfR7tg #Deno #Nodejs #Bun #CloudfareWorkers

24

New Pod! Tom Howlett, Head of Product Management at Sonar is our guest. Sonar is the leader in helping engineers write clean code through continuous feedback during the development process, and is trusted by millions of developers worldwide. We talk about: - The idea of "Start Left" and how it ties into "Shift Left" - Gen AI in developer workflows and how it promotes TDD - How does Sonar empower development teams? What's the role of the PM? - What constitutes a bad test? - Will static code analysis ever eliminate the need for pen testing? - How can static code analysis catch bugs across integration boundaries? - What does a team at Sonar look like? - Is there a QA or BA role at Sonar? - What makes Sonar a great place to work YouTube: https://bit.ly/3Xfv2bp Apple Podcasts: https://apple.co/4bNrAJK Spotify Podcasts: https://spoti.fi/4bZjtcA LinkedIn Group: https://bit.ly/3wZIWDM RSS Feed: https://bit.ly/3KsaODW Twitter: https://bit.ly/4ecWHju https://lnkd.in/gP2jpeZc #cleancode #sonar #continuousdelivery #teamdynamics #shiftleft #dx

23

1 Comment

➰ APIContext's latest insights on cloud-based API performance have been featured on Nordic APIs! In the 2024 report, we delve into crucial aspects affecting API efficiency: 🔐 Authentication is key. Ensuring robust authentication mechanisms in APIs is crucial, yet offloading this function can introduce complex challenges. 📖 DNS configurations matter. How you handle DNS settings can significantly impact API performance, particularly when tied to authentication processes. 🌐 The role of third parties. Critical third-party services play a significant role in 🔗 API transactions, underscoring the need for careful integration and monitoring. ⛅ Not all clouds are created equal. Differences in cloud services can drastically affect API performance, an essential consideration as APIs account for over 80% of all internet traffic. #APIs #CloudComputing #TechInsights #APIContext

15

1 Comment

Leading Cross-Org Tech Reviews Josie has written a great post about driving a cross-org multi-team tech review practice. It's very focussed, as only senior principal-level engineers are usually tasked with those projects. I do think that org leaders as well as senior engineers will benefit from reading the article and adopting the best practices described there. It's also an excellent example of how to scale one person's efforts across multiple team, and thus applies to more than just tech surveys. Project planning, roadmaps, and tech explorations all have the common characteristic of standardized templates, parallel execution, and open questions. Read on here: https://lnkd.in/gX6bnXzq

19

I'm working with a team in Go and they have these "err != nil checks" everywhere. To me it's a really big smell. I'm not familiar enough with Go to know better though. Feels like in the InitialCall if there's an error a Functional Null Object Pattern should apply. Any Golang experts want to offer up some constructive help? Note, everything has been abstracted out, so don't try to make too much sense of what the code is doing.

347

398 Comments

Trying to hire a junior to mid-level engineer in Scotland with great benefits and remote working is hard... https://lnkd.in/eQNHVqGR Not because the role isn't attractive (you'd be working on exciting large-scale system infrastructure challenges writing code with Golang - 1,000's of Kubernetes clusters, 10,000s of cloud VMs) or because the team are all crazy (they're thought leaders in their field including multiple upstream Kubernetes contributors from 3 continents!)... you got me... maybe there's a little crazy - but only the good kind! No... my challenge is whether this AI-generated image to go with my LinkedIn post makes any sense! I never have much luck with images containing generated text. Even using prompts like "spell check any text" or as is the case with this one "do not include any text" doesn't seem to work. Not to mention, I know what a Scottish Terrier is... but that "thing" in the bottom right looks more like an angry, tartan-wearing Capybara. Comment below for your biggest concerns with this image... or if you're a junior/mid-level, talented software engineer based in Scotland - maybe just skip over the image and apply online - https://lnkd.in/eQNHVqGR

62

12 Comments

Returning to Java from Kotlin has me thinking again about nulls and null-safety. Kotlin has softened me somewhat on the subject of nulls, because its handling of them is safe and elegant: declaring a type as T? is more or less equivalent to declaring it as Maybe T in Haskell, and null is just a compact representation of None in that case. The compiler will simply reject anything that tries to pass null, or the unchecked value of a variable of nullable type, to a non-nullable receiver. It's one of the two things about the language I'm really going to miss (the other being the Ruby-like block syntax). After a phase of thinking Optional<T> should be used to do the same thing in Java, I'm actually swinging back more towards annotating optional fields and parameters as @Nullable, and relying on tooling (the IDE, build-time linting) to enforce Kotlin-like null-discipline. But there's a skeleton in the closet: older (pre-record-type) Java often has a lot of POJOs with default no-argument constructors lying around. You construct one, everything's null, you set fields one by one with the setters. It's much harder to impose null-discipline of any kind in this scenario. People depend on this behaviour, too - they create test value objects by newing up instances of POJOs and setting only the fields the code under test is interested in, and everything works. You can say "you should make it impossible to construct an object in an invalid state" all you like, but you're going to break all those tests if you actually take the ability to partially populate a value type away from them. Lombok doesn't help, either - there's no way to compile-time check that all the mandatory fields have been added to a builder before calling build(). And even with record types, the ability to use builders to supply field values by name, rather than relying on their order in the constructor signature, is going to be hard to take away from people working with value types with a dozen or more fields. Java is just an ever-burning tire fire around these issues, and always has been, and it's a major reason why "legacy" code tends to suck so much. At the moment the best I think I can do is try to promote a general pattern: if you can't ensure correctness on construction, validate correctness immediately after construction (and prevent illegal mutation after that). At least then you can eliminate ad hoc null checks downstream of validation, and be clear about when missing values are actually to be expected.

84

34 Comments

Too many 'software engineers' today are glorified code monkeys. Harsh? Maybe. True? Absolutely. - 90% can't explain how their code runs in production - 95% have never touched a database outside their ORM - 99% think 'infrastructure' is someone else's problem News flash: AI is coming for your job, one-trick pony. The future belongs to the curious. The explorers. The 'how does this whole thing work' nerds. Why? Because they'll be conducting the AI symphony while you're still tuning your one-string banjo. Here’s 4 signs you're on the endangered list: 1. Your knowledge of DevOps doesn’t go beyond merging your own PR 2. You've never SSH'd into a server (it's not a disease, I promise) 3. Your debugging process is 'console.log' and pray 4. You think scaling means adding more if-else statements Embrace curiosity. Break things. Ask 'why' until your team wants to mute you on Slack. Because in the AI future, the curious engineer doesn't just survive. They thrive. P.S. If this post made you angry, you might be a code monkey. Don't worry, there's still time to evolve. 🐒→🧑‍💻

145

45 Comments