| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Before You Push: Implementing Quality Gates in Your Software Project |
| |
| |
| This post discusses best practices for automated testing in software engineering, including unit tests and integration tests for databases, APIs, and emulators. It also covers end-to-end tests using tools like Cypress, Appium, Postman, and more. Additionally, it highlights the importance of environment isolation, using Docker containers and Terraform for deployment consistency across different environments. |
|
| |
|
| |
|
| |
| Partitions, Sharding, and Split-for-Heat in DynamoDB |
| |
| |
DynamoDB starts to grumble when a single partition gets hit with more than 1,000 WCU. To dodge throttling, writes need to fan out across shards.
Recommended move: start with 10 logical shards. Watch CloudWatch metrics. Dial N up or down. Let burst and adaptive capacity buy you breathing room - until Split-for-Heat kicks in and shuffles partitions. |
|
| |
|
| |
|
| |
| Building Mac Farm: Running 2000+ iOS Pipelines Daily |
| |
| |
| At Trendyol, they run over 2,000 iOS pipelines daily across 130 Mac machines, executing 50,000+ unit tests and 10,000+ UI tests for their iOS apps. The team initiated a mobile CI transformation to address the challenges of scale and performance as their team grew and AI usage increased. They built a macOS farm from scratch with a system topology consisting of critical layers including the Host Agent, VM Agent, User Terminal, and Server. They also optimized their GitLab CI pipelines by creating common pipelines for all repositories and implementing a log structure without unnecessary parts. |
|
| |
|
| |
|
| |
| How to Get Developers in Your Team to Contribute to Your Test Automation |
| |
| |
A fresh blog post dives into how to get devs pulling their weight on test automation - not as extra credit, but as part of shipping code.
The playbook: tie automation work straight to the definition of done, clear up who owns what, and stop pretending delivery pressure is a mystery. The big idea? Most “why aren’t tests written?” problems aren’t technical. They’re cultural. |
|
| |
|
| |
|
| |
| Inside the GitHub Infrastructure Powering North Korea’s Contagious Interview npm Attacks |
| |
| |
| The Socket Threat Research Team has been following North Korea’s Contagious Interview operation as it targets blockchain and Web3 developers through fake job interviews. The campaign has added at least 197 malicious npm packages and over 31,000 downloads since last report, showcasing the adaptability of North Korean threat actors to modern JavaScript and crypto development workflows. The recent wave of malicious npm packages exposes a delivery stack that leverages GitHub for hosting malware-serving code, Vercel for payload delivery, and a separate command and control (C2) server for data collection and tasking, highlighting how threat actors are exploiting npm to target developers. |
|
| |
|
| |
|
| |
| Building a Blockchain in Go: From 'Hello, Block' to 10,000 TPS |
| |
| |
A new Go tutorial shows how to build a lean, fast blockchain - clocking ~10,000 TPS - without the usual bloat. It covers the full stack: P2P networking, custom consensus, and proper state management.
No unbounded mempools. No missing snapshots. Just a chain that actually runs, benchmarked on real machines - not theory. |
|
| |
|
| |
|
| |
| Confessions of a Software Developer: No More Self-Censorship |
| |
| |
A mid-career dev hits pause after ten years in the game -realizing core skills like polymorphism, SQL, and automated testing never quite clicked. Leadership roles, shipping products, mentoring junior devs - none of it filled those gaps.
They'd been writing C#/.NET for a while too. Not out of love, just chasing a stack shift that got rolled back months later. Classic. |
|
| |
|
| |
|
| |
| Why we're leaving serverless ✅ |
| |
| |
| Every millisecond matters in the critical path of API authentication. After two years of battling serverless limitations, the entire API stack was rebuilt to reduce end-to-end latency. The move from Cloudflare Workers to stateful Go servers resulted in a 6x performance improvement and simplified architecture. The transition enabled self-hosting, platform independence, and eliminated complex caching workarounds. |
|
| |
|
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
