2+ week, 20+ hour ago (59+ words) [nicolasbonnici] How to create a REST API in seconds Nicolas Bonnici " Nov 15 #howto #api #rest #go Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well...

1+ week, 5+ day ago (200+ words) So yesterday i started working on my chess engine, written in c++,i'm writing these blogs and a couple more i'll write in the future for quite a selfish reason (to track my progress) and also because i want someone else, confused like me in the future to use this, hopefully, as a road map to write their engine. right so i started yesterday, i started with well board representation, I'm a programmer not a writer so please forgive my fuck ups here and there, some times i won't make sense but lie to yourself and pretend you do understand what i'm on. ` from there i basically hard-coded each each in the 8x8 array. and then proceeded to have print function, which prints the pieces on the console, it maps a string i hard-coded to the enum values. 1.pieces = " PNBRQKpnbrqk" it…...

2+ week, 3+ day ago (249+ words) If you've ever deployed a React app and seen something like "served via NGINX' but didn't quite know what that means " this guide is for you." This is Part 1 of my series: " Mastering NGINX for Frontend Developers " From Zero to Production." We'll go from not knowing what NGINX is " to confidently using it to deploy and scale your frontend projects. NGINX (pronounced engine-ex") is a high-performance web server that can also act as a: It's used by companies like Netflix, GitHub, Airbnb, and most likely " your favorite React app. Even if you're not managing servers day-to-day, understanding NGINX helps you: In short " it's the bridge between your frontend code and the real world. Here's what a typical deployment looks like: So NGINX becomes your traffic controller " it knows what to serve and where to forward requests. Let's peek under the hood…...

4+ week, 1+ day ago (366+ words) I have been using this little tool for a bit because I don't always get to have docker in some of the specialized environments or platforms I build for. I decided to polish it up and release it. This complexity multiplies when you're working on multiple projects. Context switching becomes painful, and onboarding new developers means sharing a 50-step setup guide. Realm is a single CLI tool that replaces your entire development environment setup. It combines: All written in Rust for speed and reliability. Getting started is simple: Pre-built binaries are available for macOS (Intel & Apple Silicon), Linux (x64 & ARM64), and Windows. The interactive init experience makes setup effortless: Realm acts as a single command center for your entire development environment: Instead of manually configuring nginx or dealing with CORS issues, Realm's built-in proxy handles everything: Like Foreman or Overmind, but integrated…...

2+ week, 2+ day ago (64+ words) [OWASP" Foundation] OWASP Cornucopia 3.0 - A call for card game designers! Johan Sydseter for OWASP" Foundation " Nov 13 #gamedev #security #design #webdev Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well...

2+ day, 2+ hour ago (358+ words) Great DevOps isn't built on powerful tools , it's built on developers who have the freedom and clarity to use them well." Developer Experience (DX) refers to how developers feel while interacting with tools, processes, documentation, and systems throughout the development lifecycle. A good DX means developers: DX isn't about giving developers more perks" , it's about improving efficiency, reducing friction, and enabling innovation. Developer Experience and DevOps are deeply connected. DevOps aims to shorten the development lifecycle and improve collaboration through automation and cultural transformation. DX ensures developers actually enjoy , and succeed , within that system. How DX Elevates DevOps: In short: Better DX = Happier Devs = Better Software + Faster Delivery. 1. Documentation That Actually Helps " Clear, updated, concise documentation saves time and confusion. 2. Fast Feedback Loops " Slow builds or testing cycles kill motivation. Fast pipelines keep devs moving. 3. Automation of Repetitive Tasks " CI/CD,…...

6+ hour, 15+ min ago (527+ words) The world of software delivery has changed forever. Gone are the days of isolated dev and ops teams exchanging endless tickets. Now, speed, collaboration, and automation rule. At the center of this evolution stands DevOps " a movement reshaping how software is built, tested, and deployed. Imagine this: your development team pushes new code at 10 a.m., automated tests validate the changes, infrastructure scales dynamically, and within minutes, users see the update. That's the kind of magic DevOps enables " powered by the right tools. Let's embark on a practical tour through 20 essential DevOps tools every modern organization should know. Jenkins remains the heartbeat of continuous integration and delivery. It automates building, testing, and deploying code so developers can focus on innovation rather than manual work. With over a thousand plugins, Jenkins fits into nearly any tech stack imaginable. Both enable teams to integrate…...

1+ week, 2+ day ago (81+ words) This version fixes several key issues to ensure the stable operation of the library: You can use the following command to get the latest version: TIP: This is a potential breaking change in this release, please check and update your references before upgrading. We thank all contributors for their efforts in this release! If you find any issues or have feature suggestions, please feel free to open an issue at GitHub Issues. Enjoy the new features and improvements in v0.7.2...

1+ week, 15+ hour ago (118+ words) I've been pretty obsessed with Go lately. I had an old blog that was created using Jekyll + Github Pages, but I wanted something with less "batteries included" for my website. I also wanted to have an active count of likes and views for my posts, as this would motivate me. I decided to use Go to build a Hybrid Site Generator. Not sure if that is an actual term, but let me define it: My Go app has 2 components: I had a really fun time learning how to create this in Go. I wrote more in-depth about it here: Go Blog Have any thoughts or feedback? By the way, I'm considering adding comments as well :)...

1+ week, 3+ day ago (443+ words) Rate limiting is essential for protecting APIs from abuse, ensuring fair resource allocation, and maintaining system stability. While there are existing solutions, I wanted to build something lightweight, performant, and easy to integrate into any Go project. Today, I'm sharing kazrl - a zero-dependency rate limiter library that implements three different algorithms and comes with ready-to-use middleware for popular Go web frameworks. Most rate limiting libraries either: I needed something that: That's it! No transitive dependencies to worry about. Here's the simplest way to add rate limiting to your HTTP handler: That's literally 10 lines of code to add rate limiting! Perfect for APIs that need to allow bursts while maintaining average rate limits. Use case: Public APIs, user-facing endpoints Smooths out traffic spikes by processing requests at a constant rate. Provides the most accurate rate limiting without fixed window edge cases....