@maciej_pyrc did the same, best refactor we made. one catch: make sure async handlers actually reach it. on express 4 a rejected promise that nobody awaits skips the middleware completely, and you're back to a hanging request with no log
@runbund selling consulting clients on coding projects just to get on-the-job xp is the real playbook here. most people wait for permission to get experience, you made the job create it
most senior skill i've picked up this year:
saying "it depends" in a design review
then pausing, looking at the whiteboard, and letting everyone else figure out what it depends on
@MansiCodez "handles agent failures" is the line doing all the work here. same job as today honestly, the 3am page just says "agent retried 40 times and opened 12 PRs" instead of "null pointer at line 88"
@Nileshblog idempotency keys are one of those things you only add after the first double charge. one gotcha: store the key with the response, not just a seen flag, so a retry gets the same answer back instead of a 409 the client doesn't know what to do with
@devcauemoreira backend. every one of the others still needs it underneath: AI is mostly APIs, queues and caching around a model, security is mostly understanding how backends break. learn it properly and switching later is cheap
@RadhaDasi__ because banks, service companies and most big backends still run on java + spring, and nobody updated the syllabus. good news: spring boot + one real project with a db and auth is ~2 months of evenings. start in 2nd year and you're already ahead
sunday 8:45pm: "let me just quickly bump node to the latest LTS"
9:30pm: rewriting a jest config, googling an ESM error and reading a github issue where the top comment is "+1" from 2023
it was not quick
@RawalD93 watching gradient descent actually roll downhill teaches more than 3 pages of partial derivatives. bookmarking this for the next time someone asks me how backprop works and i pretend i still remember
@foyonaczy this is why every image pipeline needs a policy.xml that blocks PS, EPS, PDF and XPS by default. and check magic bytes, not the extension. a .jpg is whatever the file says it is, not whatever the user named it
@biki__das inference engineering is still backend though. batching, queues, caching, timeouts, p99 latency... same problems, just with a far more expensive server and a GPU bill that makes you check it twice
@Mohitvermacode7@ChaiCodeHQ@piyushgarg_dev@nirudhuuu@Hiteshdotcom middleware order is the one that bites later. a body parser or auth registered after the route just silently never runs for it. and always call next() or send a response, a middleware that does neither leaves the request hanging forever
kaya update:
it can read my whatsapp now, it just can't answer yet
tonight's plan: wiring the first reply loop so it actually talks back instead of reading my chats like a nosy cousin
@Mudassir338 k8s will happily restart the pod 400 times. it has no idea the real problem is a bad config that went out to every replica, or the db running out of disk
automation fixes the symptom, on-call fixes the cause
@voidyaps if P = NP gets proven, every password and every bank's encryption is suddenly on the clock
and i'll still be waiting 40 minutes for CI to tell me i missed a semicolon
@birdabo threejs demos are the new todo app benchmark. looks insane in a 20 second clip, then you ask it to keep the physics stable for 2 minutes and the cube phases through the floor
@ZoroTheBuilder@Ansenjeo this is honestly the best way to learn anything. rebuild a tiny version of the thing that broke your brain. how are you running the game loop, server ticks or all client side?
honest question: does anyone actually know what's in their .gitignore
mine still has entries for tools i stopped using in 2024 and i'm too scared to remove a single line
@level38_co devops to running an offline cleaning business is honestly the same job, just with real mops instead of kubectl. welcome to X andrii, curious what you're building now
@ShivamSi1404 start simple: one page in react or even plain html + fetch, enable CORS on your backend for that origin, and make your API return clean json errors. get one screen talking to one endpoint first, then grow it from there