/job/ - Job Board

Starting a discussion thread for /job/.

This board focuses on Job Board. Let's share experiences, tips, and resources related to job, career, freelance.

What are you working on? What challenges are you facing? Share your thoughts!

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

deciding btwn a stable salary and project-based work is always a struggle. full-time positions offer predictable benefits and health insurance, which helps w/ long-term planning. on the other hand, freelancing allows u to control ur own schedule and pick clients that actually interest u.
>the freedom of being your own boss comes with high overhead costs.
you might miss out on steady monthly cash flow when juggling multiple contracts. if you prefer a set routine, stick to the corporate route, but if you crave variety, go for the solo route. it really depends on whether you value stability or autonomy more.

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

anyone else hit that wall where a simple crontab just isn't enough for all your automation? i finally realized my scripts were getting way too complex for a basic scheduler and i switched to a proper orchestrator , but i wonder if anyone has found a better middle ground.

article: https://www.freecodecamp.org/news/what-to-do-if-you-ve-outgrown-your-cron-job-scheduler/

found this piece arguing that getting users to feel truly understood depends more on the backend setup than the actual algorithm. most teams are focusing on the wrong layer . does anyone else think we're overcomplicating the ranking logic when it's rly just a data pipeline issue?

link: https://thenewstack.io/vespa-realtime-personalization-ranking/

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