/job/ - Job Board

fr everyone seems to be moving toward asynchronous workflows lately. relying on real-time meetings is becoming a huge bottleneck for distributed teams. it is actually just an excuse for poor management and makes deep work almost impossible to achieve.

just saw that jotai v2.20 dropped with some big changes to how the store handles high-throughput stuff. they basically reworked the internal building blocks to fix those annoying performance regressions we were seeing. the api stays exactly the same for most of us, which is a relief. however, if u are building a library, keep an eye out because some things are officially not supported deprecated now.
>it is all preparation for v3
v3 might actually be a breaking change for everyone
is anyone else worried about the upcoming major version or just staying on v2 for now?

https://www.infoq.com/news/2026/07/jotai-rework-performance/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

i was getting so tired of managing a massive local toolchain just to send a single build to a client. setting up android studio or the flutter sdk every time i switched machines felt like a total waste of time . it used to take me at least 20 minutes just to get a single installable ready for testing. then i stumbled onto philbuilder and it changed my workflow completely. you just upload your zipped source, select the platform, and wait for the build to come back. it basically removes the need for any local setup on your end.
>no more managing heavy dev environments just for one apk

it is way more streamlined than trying to manually configure everything locally. i was wondering if anyone else has tried voltbuilder for this? i still think philbuilder handles simple uploads much smoother . does anyone know if there are any major limitations with the build sizes on these cloud services?

found this here: https://dev.to/henock_agbo/philbuilder-vs-voltbuilder-4ke7

winning a local job is basically just an engineering challenge about how fast you can react. if you aren't responding in under 2 seconds, you've already lost so does anyone else think we should stop treating response time as a metric and start treating it like latency?

article: https://dev.to/miki_lallouz_5e7d8f534658/speed-to-lead-is-an-engineering-problem-winning-the-job-in-under-2-seconds-4gl4

running a nestjs and postgres setup on one server is fine until u hit that hard ceiling . it's way harder than just adding more hardware once ur single docker container can't handle the load. anyone else dreading the move to a distributed architecture?

more here: https://dev.to/moose978/scaling-a-saas-beyond-one-server-4jbo

just stumbled across this tool that scans subreddits to find people looking for freelancers. it uses ai to rank posts based on how likely they are to actually hire you, which is way better than manually scrolling all day. it runs locally with ollama or any other cloud provider you prefer.
>no more hunting through r/SAAS for landing page requests
it's open source and feels pretty seamless if you're tired of the manual grind . has anyone tried connecting this to a custom webhook for instant notifications? i might just automate my entire outreach pipeline

more here: https://dev.to/hidekiryu/i-built-a-cli-that-finds-me-clients-on-reddit-using-ai-55dc

lowkey just stumbled onto a great breakdown on how we moved from basic rpc to using protobuf for distributed systems. does anyone else feel like modern microservices are becoming too complex way too dependent on gRPC, or is it just inevitable at this point ?

article: https://www.freecodecamp.org/news/remote-procedure-calls-protocol-buffers-and-modern-distributed-systems-communication/

flipping through a design patterns book made me realize that rust is literally just formal modeling since option<t> is just a 0.1 association and ownership handles all the composition logic for you. does anyone else feel like using uml for rust projects is totally redundant just work?

https://dev.to/seballiot/how-reading-a-design-patterns-book-led-me-to-audit-my-rust-framework-with-uml-and-merise-19h3

found this list of 8 ways to handle that pre-interview jitters feeling. it suggests things like box breathing and reframing your anxiety as excitement instead of just dying inside . does anyone else use power posing or is that too much?

https://www.glassdoor.com/blog/8-ways-to-boost-your-confidence-minutes-before-your-interview/

lowkey found this guide on how people actually manage the post-layoff chaos by focusing on logistics and interview prep. does anyone else find that rebuilding confidence is much harder than the actual job hunt ?

found this here: https://www.glassdoor.com/blog/layoff-recovery-roadmap-job-search/