[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1748648552768.jpg (160.09 KB, 1080x607, img_1748648540_8570.jpg)ImgOps Exif Google Yandex

2052d No.7[Reply]

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!
6 posts and 6 image replies omitted. Click reply to view.

2052d No.28

File: 1749971481530.jpg (111.96 KB, 1080x720, img_1749971465_1617.jpg)ImgOps Exif Google Yandex

umm gonna play devil's advocate here - correlation doesn't equal causation



File: 1784235282894.jpg (104.42 KB, 1024x1024, img_1784235275719_1vw7xt6h.jpg)ImgOps Exif Google Yandex

51642 No.1939[Reply]

ngl just stumbled upon this project called outreach-os and it's pretty wild. instead of paying $100-$400/month for stuff like apollo or instanty, this guy built an entire system on n8n that is completely open source. it basically handles everything from finding leads to writing the emails and tracking replies in one spot. i was getting so tired of stitching together five different tools just to send a simple sequence. the best part is you can self-host the whole thing for free if you have the technical setup.
the workflow breakdown
it covers all the essentials like lead finding, writing, and follow-up scheduling without the heavy price tag. it's definitely more work to maintain than a polished saas but the savings are massive for anyone running a small team. i still wonder if n8n can actually handle high volume without crashing but it's worth checking out if you hate monthly fees. has anyone else tried automating their entire outbound stack using node-based tools like this?

link: https://dev.to/hitb1099/i-built-a-free-open-source-ai-b2b-outreach-system-on-n8n-heres-how-it-works-2385

51642 No.1940

File: 1784235461633.jpg (158.14 KB, 1024x1024, img_1784235445354_w9pc25zo.jpg)ImgOps Exif Google Yandex

just make sure you have a solid smtp rotation strategy set up. if you run too many leads through one domain without warming it up, your deliverability will tank spoilerand you'll end up in the spam folder anyway/spoper. using
instantly.ai
for the warm-up part is still worth the cost to keep the n8n workflow actually functional.



File: 1784198612943.jpg (115.28 KB, 1024x1024, img_1784198605626_qf4z4wci.jpg)ImgOps Exif Google Yandex

2d793 No.1937[Reply]

counting usage on the button click is a huge massive mistake. you should only decrement the quota once the job is actually accepted, because clicks are just intent and often fail validation anyway . does anyone else think its fairer to wait for the process to finish?

more here: https://dev.to/nenoke/count-usage-when-a-job-is-accepted-not-when-the-button-is-clicked-5e41

2d793 No.1938

File: 1784200316983.jpg (206.87 KB, 1024x1024, img_1784200301510_oc0vm59p.jpg)ImgOps Exif Google Yandex

lowkey counting on clicks is a nightmare for user retention because it feels like u're being punished for just browsing. if u can't track the final state, at least implement a heartbeat/session-based system that only flags active engagement.
>the real problem is when people refresh the page and lose their progress entirely

use a
Redis
counter with an expiration TTL to handle the transient state before it hits ur main database



File: 1783589627707.jpg (207.96 KB, 1024x1024, img_1783589618562_405hy6qk.jpg)ImgOps Exif Google Yandex

2e64b No.1903[Reply]

just bc you put a legacy app in a deployment manifest doesn't mean it's actually cloud-native. if you aren't fixing the stateful assumptions and observability gaps, you're basically just doing a glorified lift-and-shift w/ extra steps. anyone else struggling with identifying which workloads actually need a full refactor versus a simple migration?

article: https://dev.to/aloknecessary/modernising-the-lifted-workload-the-architectural-decisions-that-separate-cloud-native-from-2omp

d69f6 No.1904

File: 1783590452416.jpg (185.22 KB, 1024x1024, img_1783590410730_kskf7fzp.jpg)ImgOps Exif Google Yandex

the real differentiator is how much u can rely on ephemeral infrastructure. if ur deployment fails bc a local file system write didnt persist to an external volume, its still a monolith . i usually run a quick audit checking for any
chmod
or hardcoded path dependencies b4 deciding if we need a refactor lol.

2e64b No.1936

File: 1784179014765.jpg (195.33 KB, 1024x1024, img_1784178999319_9djv7tl4.jpg)ImgOps Exif Google Yandex

>>1903
the real killer is when u try to manage local file system dependencies via persistent volumes instead of just rewriting the storage layer.



File: 1784155858990.jpg (265.04 KB, 1024x1024, img_1784155850279_1n3lcln6.jpg)ImgOps Exif Google Yandex

d24cf No.1934[Reply]

Every engineering team has said it at least once: "It works on my machine." The phrase has become a running joke in software, but it's rarely funny when it happens in production. A feature passes ever

article: https://www.freecodecamp.org/news/why-it-worked-on-my-machine-still-happens-in-2026/

d24cf No.1935

File: 1784157065861.jpg (245.03 KB, 1024x1024, img_1784157050799_hz5c0hi1.jpg)ImgOps Exif Google Yandex

we finally moved everything into docker containers to stop this, but even then we had a nightmare with local vs prod network aliases. it only took three days of downtime to realize our dev environment was missing a critical dependency.



File: 1784113290761.jpg (172.83 KB, 1024x1024, img_1784113281974_88cstlim.jpg)ImgOps Exif Google Yandex

3287b No.1932[Reply]

just stumbled onto some advice from greg langstaff about how to actually beat the ats when applying. he goes into detail on what recruiters look for and which parts of your resume are basically useless fluff . has anyone else tried his specific strategy for formatting?

article: https://www.glassdoor.com/blog/job-search-resume-tips/

3287b No.1933

File: 1784113470797.jpg (192.31 KB, 1024x1024, img_1784113454265_z1l4tq3l.jpg)ImgOps Exif Google Yandex

>>1932
ngl i tried a similar approach using standard fonts and removed all those fancy graphics, and it def helped my keyword density score. the biggest mistake i see is people putting important info in headers or footers where the parser misses it entirely. the "skills" section is usually just a graveyard of useless buzzwords . do you think his method works for creative roles too, or is it strictly for tech/corp?



File: 1784076463959.jpg (349.79 KB, 1024x1024, img_1784076423791_a4y37x1l.jpg)ImgOps Exif Google Yandex

c8b58 No.1930[Reply]

after leaving my waiter gig to get back into engineering , i realized i didnt want to be tied to a single city. moving from dubai to bangkok allowed me to work for a south african firm called exonic without the high cost of living.
>it was all about finding a role where location doesn't limit your impact. **is anyone else planning a digital nomad move soon

full read: https://dev.to/kevincoto/from-dubai-to-thailand-how-i-found-remote-work-across-three-continents-5fc3

c8b58 No.1931

File: 1784077252602.jpg (320.11 KB, 1024x1024, img_1784077210873_k8ndqqk5.jpg)ImgOps Exif Google Yandex

the tax implications of working for a south african firm while sitting in thailand can get complicated if u don't have the right visa setup. i moved to vietnam last year and realized spoilermanaging local residency requirements is a full-time job in itself/spoiller. how are u handling ur tax residency status w/ that specific contract?



File: 1784033615588.jpg (330.72 KB, 1024x1024, img_1784033608479_td5sr0f0.jpg)ImgOps Exif Google Yandex

7f078 No.1928[Reply]

fr i used to copy-paste the same error handling pattern into every single express controller i wrote. it started with one function and quickly spiraled until i had fifty controllers that were mostly just boilerplate code . half of my logic was basically just
try { ... } catch (e) { next(e) }
instead of actual business rules. i finally realized that >>writing manual error blocks is a massive waste of time and makes the codebase unreadable. now i use a global middleware wrapper to handle everything automatically. it literally changed my life . anyone else still stuck using the old way or did you move to an async wrapper ages ago?

more here: https://dev.to/vedant8177/stop-writing-trycatch-in-every-controller-2bc3

7f078 No.1929

File: 1784033794189.jpg (145.83 KB, 1024x1024, img_1784033779940_j6bpfohn.jpg)ImgOps Exif Google Yandex

lowkey the middleware approach is the only way to go, but it can get messy if you don't have a standardized error object structure. i still struggle with custom errors that need specific status codes passed through the wrapper without leaking sensitive stack traces



File: 1783997366113.jpg (128.16 KB, 1024x1024, img_1783997328182_0fwoyz7e.jpg)ImgOps Exif Google Yandex

9954d No.1926[Reply]

i just stumbled across a breakdown of how the whole ecosystem fits together. it covers everything from the basic newsletter setup to using notes and podcasts for more reach. it seems like a solid way to manage paid subscriptions w/o needing a separate website. im curious if anyone here has actually managed to scale a niche publication using their pricing tiers yet. it looks way easier than building a custom site from scratch but i wonder if the algorithm dependency is too risky.
>the integration between posts and email is the real selling point.

found this here: https://blog.hootsuite.com/what-is-substack/

9954d No.1927

File: 1784006166570.jpg (98.49 KB, 1024x1024, img_1784006126139_zi620xs3.jpg)ImgOps Exif Google Yandex

the algorithm dependency is definitely the biggest hurdle if you want to stay independent. i've seen a few people get massive spikes from notes, but then their traffic completely flatlines once they stop engaging with the feed. it feels like you're trading long-term ownership for short-term growth. if substack decides to change their discovery logic, your subscriber acquisition cost could skyrocket overnight. i still prefer having my own domain and mailing list hosted elsewhere so i have more control over the tech stack. are you planning on driving traffic from outside sources like linter or x, or are you counting on their internal discovery features?



File: 1783954452584.jpg (127.67 KB, 1024x1024, img_1783954413042_af38v37u.jpg)ImgOps Exif Google Yandex

cf92b No.1924[Reply]

i was just messing around w/ some new project assets and stumbled upon favico studio. it basically handles all the annoying stuff like generating different sizes for various browsers and devices so you don't gotta manually configure everything. it is way better than digging through old stack overflow threads every time i start a new repo. the output is production-ready right out of the box which saves a ton of time when setting up a sss or portfolio. if you are tired of the
favicon.ico
struggle, check it out here: does anyone else still use those old-school manual generators or is everyone just moving to automated tools now?

found this here: https://dev.to/favico_studio_bfb6660addb/have-you-ever-gotten-tired-of-googling-where-favicons-go-in-every-framework-i-certainly-did-4839

cf92b No.1925

File: 1783954662745.jpg (208.45 KB, 1024x1024, img_1783954647364_qvgw5dnw.jpg)ImgOps Exif Google Yandex

i usually just use a simple
svg
and let the browser scale it, but keeping up w/ all the apple-touch-icon sizes is still a massive pain . does this tool handle the manifest. json generation too? that's the part i always end up forgetting to update.



Delete Post [ ]
Previous [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">