Topics

Interviews, levels, offers, promotions and the performance review that said "more visibility". Salary talk welcome.

Where world events hit the industry: wars and the people working through them, elections and tech policy, sanctions, internet shutdowns, chip export rules, drones, OSINT, and how all of it lands on developers. Heated is fine. Hateful is not.

The universal excuse. Memes, shitposts and the joke that only lands if you have used git. Keep it kind.

Remote and hybrid work from anywhere. Timezone overlap, async culture, home office setups, digital nomad visas, coworking spaces, return to office mandates, and the days you do not speak to a single person.

Architecture arguments with no clean answer. Monolith or services, SQL or document, REST or RPC — bring the trade-offs, not the verdict.

Databases, query plans and the index you forgot. Postgres mostly, everything else welcome.

For people starting out or starting over. Bootcamps, self-teaching, the first job search, imposter syndrome, and the questions you are scared to ask at work. No question is too basic here.

Codebases older than your tenure. Comments from 2011, functions nobody dares delete, and the commit message that just says "fix".

Freelancing and contracting. Pricing, Upwork and Fiverr, direct clients, contracts, scope creep, chasing invoices, international payments, and the client who wanted "something like Uber but simple".

Programming humour, office horror, "it works on my machine", production on fridays, standup that could have been an email. Low effort welcome, reposts tolerated, explaining the joke is a crime.

Coding rounds, system design, take home assignments that took a week, recruiters who ghosted, offers that got pulled, and the occasional interview that went great. Prep resources and real questions welcome.

Indian developers ki community. Service company vs product company, notice period, appraisal drama, campus placements, startups in Bengaluru, Gurgaon traffic, and real tech discussion. Hindi, Hinglish ya English, jisme comfortable ho likho.

Everything that is not a screen. Running, plants, bread, sleep, and the hobby that keeps you sane between sprints.

Running your own services at home. Proxmox, TrueNAS, Docker compose stacks, Jellyfin, Home Assistant, Nextcloud, backups you have actually tested, power bills, and the rack that started as one old laptop.

Performance work, benchmarks and the microsecond you saved on a path that runs once. Measure first, brag second.

Bugs that vanish the moment someone else looks. Heisenbugs, environment drift, and the eternal "but it passed locally".

Using AI tools for real work and saying honestly how it went. Coding assistants, agents, local models, evals, costs, the jobs question, and the demo that did not survive contact with production. Hype and doom both get checked.

Data engineering, pipelines, labelling, drift, and the training set that quietly rotted.

Explain your problem out loud here. Half of you will solve it in the third paragraph and post anyway. That is allowed.

Deploys, rollbacks, feature flags and incident stories. What broke, what you changed, and what you would do differently.

Comunidad para quienes programan en español. Dudas técnicas, trabajo remoto para empresas de afuera, sueldos en dólares, freelancing, universidad y memes. Escribe como hablas, nadie te va a corregir la ortografía.

CI pipelines, Kubernetes manifests, Terraform state and the indentation that cost you an afternoon.

A support group for React developers. Hooks that fire twice, effects that never clean up, and the memo that made it slower.

Code that runs where there is no operating system to blame. Microcontrollers, RTOS scheduling, CAN bus, power budgets, bootloaders and the oscilloscope that tells the truth.

Linux on the desktop and laptop. Distro hopping, Arch installs, NVIDIA drivers, Wayland vs X11, dotfiles, tiling window managers, gaming on Proton, and helping each other out of a broken bootloader.

Raspberry Pi builds, ESP32 and Arduino projects, home automation, GPIO pain, SD cards that die at the worst moment, and the cluster of four Pis you swear is for "learning Kubernetes". Post your builds with photos.

Apps that live in a pocket. Cross-platform vs native, performance on cheap phones, offline-first, app store reviews, and push notifications people do not hate.

Centering things. Grid that will not behave. The z-index war. Beautiful layouts and the three hours it took to nudge one pixel.

Where money meets code. Double-entry ledgers, idempotent payment APIs, settlement files that do not add up, PCI scope, and the rounding bug that cost someone 0.01 a million times.

Designers and the developers who build their work. User research, design systems, handoff that does not lose details, and accessibility that is not an afterthought.

Small software businesses without a war chest. Pricing experiments, the first ten customers, churn, cold email that is not spam, and honest revenue numbers.

Modern PHP, Laravel, Symfony, WordPress plugins, legacy PHP 5 codebases that refuse to die, and the jokes. Yes, we have heard them all. PHP 8 is actually good and we will fight you on it.

Writeups, CTF walkthroughs, breach post mortems, bug bounty wins and the reports that got marked "informative". Offensive and defensive both welcome. Everything here is about systems you own or are allowed to test.

The 80%-done thing in your repos. Post it, get told to ship it, ship it. Or admit it is dead and free yourself.

For people who have re-run a pipeline "just to see". End-to-end testing, test pyramids and test trophies, Playwright and Cypress, and making CI something the team trusts again.

Show your desk. Monitors, chairs, mechanical keyboards, standing desks, cable management, and the setup you are slowly building on a student budget. Every setup is welcome, including the laptop on a pillow.

Amiga, C64, ZX Spectrum, DOS, old Macs, early Linux, emulators, recapping boards, retro game dev and the stories of how we first got into computers.

Deciding what to build, and what not to. Discovery interviews, prioritisation frameworks that survive contact with sales, roadmaps that are not promises, and working well with engineers.

TypeScript, from "why is this any" to conditional types nobody can read. Generics, inference, and knowing when to stop.

Projects you shelved, prototypes that deserved better, and the scope creep that ate them. Post the corpse, take the lesson.

Technical writing, READMEs, changelogs and API reference. The unglamorous work that decides whether anyone can use your thing.

Auth, tokens, headers, and the password rule that makes things worse. Practical security for people shipping products.

Comunidade brasileira de devs. Trabalho remoto pra fora, CLT vs PJ, faculdade vs bootcamp, Java legado de banco, React, Flutter, e reclamação sobre o trânsito de São Paulo. Escreve em português mesmo.

Reviews from people who actually paid for the thing. Phones, laptops, earbuds, smartwatches, e-readers, chargers that died in a week. Buying advice, regret, and the occasional unboxing.

The human side of open source. License changes, hostile forks, maintainers burning out, companies taking without giving back, entitled issue comments, funding, and the occasional happy ending.

Software for the energy transition. Grid carbon intensity, demand response, EV charging, emissions accounting, and the honest measurement of how much our own systems burn.

LLMs in production. Evals, retrieval, prompt regressions, and the hallucination that made it to a customer.

Keyboards, switches, keycaps and desks. Photos welcome, sound tests encouraged, roommates apologised to.

Game art, shaders, sprite work and technical art. Pretty things and the maths that makes them move.

Workers, isolates, cold starts and the 3MB bundle you are 40KB over. Everything that runs close to the user and far from a normal server.

Cooking for people who read documentation. Recipes with actual measurements, kitchen experiments, and what you ate at 2am mid-deploy.

Building software for hospitals, clinics and patients. Interoperability standards, privacy law, clinical safety, and why the nurse workflow matters more than your architecture diagram.

We talk about Unity related stuff