Damian Esteban

Learn how to write custom result builders https://lnkd.in/ehqq5XK 🧐 What are result builders? 🤩 Defining your own 🚀 Ready to use AutoLayout example #swiftlang #iosdev

7

“Codegen tools are broken.” They churn out boilerplate, need endless fixes, and rarely feel… smart. So when I asked Codebuff to create a browser-based Minecraft game, I wasn’t sure what to expect as I just told it: 👉 “generate a basic minecraft clone that runs in my browser that lets me move around in the world, explore it, and mine blocks. keep going until it's very recognizable as a minecraft game.” And here’s what happened: ✅ Hover effects to show where blocks drop. ✅ Particle effects when blocks are destroyed. ✅ An instruction overlay showing block types. Codebuff uses two agents: 👨‍💻 A Developer agent to write features. 🕵️‍♂️ A Product Manager agent to critique and refine. The best part? The game actually works. We showed a basic version to a dozen people, and each added their own ideas and features to our project. Check out the demo video for the final version. Check out our Substack post for more information: https://lnkd.in/gVFp4H69

17

Rails 7.2 now makes sure jobs get enqueued after the current database transaction is committed. Previously, your jobs would run before the records were saved to the database causing errors, so Rails takes care of it for you. If you've ever had to remind yourself (or your team) to use `after_create_commit` callbacks instead of `after_create`, this solves that problem. ActiveRecord uses transactions behind the scenes, so it's an easy mistake to make. And with jobs being retried, it's confusing why the job fails then succeeds a second later. This is another great example of conceptual compression in Rails! https://lnkd.in/gyNtiPnr #ruby #rubyonrails #rails

141

9 Comments

🏎️💨 Making of a Ridiculously Fast™ API client in R. Why my package is **~17x faster** than the community alternatives that call the **exact same API endpoints**. 👇🏽**design choices matter** ✨ https://lnkd.in/ggi_2XyQ

129

2 Comments

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

170

59 Comments

Last Call! 📣 🚂 We're gearing up for our next Observability Engineering Community London meetup, which is happening this Wednesday! This time, we've got two great talks by Dinesh Nithyanandam, Lead for Observability, Performance, and Reliability at A.P. Moller - Maersk, and Carly Richmond, Principal Developer Advocate & Manager at Elastic. 👉 Dinesh will discuss how A.P. Moller - Maersk leverages Flagger to automate canary deployments across its extensive infrastructure, which includes 120 clusters and over 1,000 microservices running in a multi-cloud environment with AKS and GKE. By integrating with monitoring tools like Prometheus, Flagger continuously evaluates key SLOs, ensuring that new versions are only fully deployed if they meet defined reliability and performance standards. 👉 Carly will draw on her experience in building applications for investment banking to explore why validating long-term feedback on feature adoption is challenging. She will discuss how combining Real User Monitoring agents, such as Elastic RUM, with OpenTelemetry tracing for backend services and Elastic Observability can help quantify user experience satisfaction and adoption, ensuring effective user experiences. 📅 Event Details: Date: Wednesday, September 11th Time: 6:00 PM Location: 24 High Holborn · London See you all there! #Observability #Engineering #SRE #SLO #devops

4

Large pull requests (PRs) are counterproductive. Here's why:  1️⃣ Architecture review at the PR stage is wayyy too late. If the design is wrong, a big PR locks you between a rock (only make minor changes and keep moving forward) and a hard place (re-implement it correctly). 2️⃣ Long PRs (think 50+ files) are hard to follow. Even if and when someone does get through it, review cycles drag on, delaying feedback and delivery. 3️⃣ Getting code “ready for review” is hard work, and big PRs can potentially have a lot of changes that throw away that work. Whether it’s duplicating work, creating merge conflicts, or focusing on non-critical parts, these inefficiencies kill momentum. 4️⃣ Big PRs contradict agile values. Agile is about delivering incrementally and gathering feedback fast. Oversized PRs? They do the opposite. Software development is an art, but we’re engineers—not solo artists. Small PRs enable collaboration, better reviews, and faster feedback, helping teams move smarter and ship faster. More thoughts on this in the link in the first comment below. How does your team handle PR size? Let’s talk about it. 💬 

35

2 Comments

Bito reviewed 600,000 lines of code last week, across thousands of Pull Requests. 10 of them were so large, they were nearly 200,000 lines of code changed. Generally, that's not a good practice. Break down your PRs into more manageable topics that can be more easily reviewed. But, they did have AI working on their reviews, so that definitely helps. AI doesn't get tired, it just methodically goes through the thousands of lines of code.

68

5 Comments

4 cool API Discovery features we released at Akto.io last month 1. logical API grouping — automated API Groups based on functionality and risk 2. staging, QA, dev, UAT and production API grouping — automated API groups based on env 3. old API versions grouping — automated shadow APIs and old API versions grouping 4. custom API grouping — create your own custom API groups

23

"It takes too long", "it slows me down", "you can't design software that way", "it doesn't fit my feature" - I've heard all these in the past and my usual response is "give it a try". Experimentation is a key part of R&D - sometimes we succeed, sometimes we fail, but we always learn from it. And that's not just restricted to a department looking at new tech or processes - it's just as important (maybe more so) for an individual looking to improve themselves. So if you've never used TDD before (or fallen off the wagon) then go on, give it a go ;)

12

If you needed one more reason to use TypeScript in 2025, it looks like every single AI tool works better with it than regular JavaScript. For everything beyond weekend projects TypeScript is the clear choice.

3

1 Comment

Got an email "GCP's Apache Kafka service is now live" at noon. After dinner, spent half an hour confirming it works well with Timeplus. I don't think you can make the bootstrap server publicly accessible. Has to setup a bastion host or run your app within the same project/VPC. Setting up the SASL username/pwd was not easy. Follow the guide carefully https://lnkd.in/gcKEVh3g and you may need to disable the iam.disableServiceAccountKeyCreation Anyway, if your workload are in GCP already, having such Kafka service in GCP is nice way to burn your cloud credits. Yet another Kafka vendor, great.

33

2 Comments

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

As software engineers, staying on top of emerging technologies is crucial. Today, I explored the intricacies of microservices architecture, and I’m continually amazed by the flexibility and scalability it brings to our projects. If you are looking to enhance your system’s performance, microservices might just be the solution you need. Let’s connect and share insights! #SoftwareEngineering #Microservices #Innovation"

2

**Drumroll** The sequel to Cracking the Coding Interview is coming... Jan 2025! Announcing pre-orders for Beyond Cracking the Coding Interview: Pass Tough Technical Interviews, Get Noticed, and Negotiate Successfully. Pre-order now on Amazon.com (https://lnkd.in/gCH4VSGJ), or check out more details at BeyondCtCI (http://www.BeyondCtCI.com). What's new? * 13 new technical topics—including sliding windows, prefix arrays, and rolling hashes * 150+ new problems, ranging from popular current questions to fresh twists on the classics * Three awesome new co-authors: Mike Mroczka, Aline Lerner, Nil Mamano

522

19 Comments

This post provides additional examples to JAX's documentation of vmap, illustrating how the two parameters, in_axes and out_axes, influence vmap's behavior. These examples help me better understand and internalize the functionality of vmap.

33

2 Comments