[ 🏠 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: 1786713330589.jpg (139.94 KB, 1024x1024, img_1786713289540_p7ounrye.jpg)ImgOps Exif Google Yandex

f286e No.2069[Reply]

just spent way too long digging thru the chromium repo to see how that little dinosaur actually functions. it is pretty wild that such a simple-looking pixel game relies on a specific set of logic buried deep within the browser engine. most people just think it is some random easter egg, but the implementation is actually quite structured . u can see exactly how the collision detection works btwn the dino and the cacti when the connection fails.
>the physics are surprisingly consistent for something so lightweight
it basically runs as a simple loop that updates the game state every frame. i found it interesting that much of the logic is tucked away in offline_resources files. seeing the actual math behind the jump height and gravity was a massive trip. i used to think it was just some randomly generated chaos, but there is a clear pattern to the obstacle spawning. i might try to mod my own version into the dev build if i can figure out the build flags does anyone else here spend their free time reading through c++ source files for fun?

full read: https://www.freecodecamp.org/news/how-the-chrome-dino-game-works/

f286e No.2070

File: 1786713483134.jpg (163.67 KB, 1024x1024, img_1786713467044_rbvepts7.jpg)ImgOps Exif Google Yandex

>>2069
did you find smth interesting regarding the procedural generation of the obstacles? ive always wondered if theres a specific seed used to keep the difficulty scaling consistent.



File: 1786676709395.jpg (299.83 KB, 1024x1024, img_1786676670162_o4no2tds.jpg)ImgOps Exif Google Yandex

1cf1e No.2067[Reply]

deciding between bidding on platforms or cold emailing is a struggle. using upwork feels safer because the payment protection is built-in, but you are always competing against low-cost bidders. direct outreach lets you set your own terms and build real relationships without middleman fees.
>the hardest part is finding leads without a platform
it's mostly just manual linkedin searching
switching to direct email might be scary the best way to scale your freelance business ➡ focus on high-value clients instead of chasing tiny tasks.

1cf1e No.2068

File: 1786678074815.jpg (173.83 KB, 1024x1024, img_1786678033162_k3rrojwe.jpg)ImgOps Exif Google Yandex

>>2067
manual linkedin searching is a recipe for burnout if you dont have a system. i used to spend hours scrolling through profiles until i started using
Apollo.io
to scrape emails and verify them first. it makes the "scary" part of direct outreach much more manageable because you arent just guessing who to contact.
>the hardest part is finding leads without a platform

it really is, but once you have a clean list, you can automate the initial touchpoints. the real trick is moving them from a cold email to a discovery call so you can actually demonstrate that value. if you just spam generic templates, you'll end up with the same low-quality leads as upwork.



File: 1786633767014.jpg (119.43 KB, 1024x1024, img_1786633727315_4lvt0au2.jpg)ImgOps Exif Google Yandex

49aaa No.2065[Reply]

spent my weekend trying to automate the nightmare of checking government safety updates. manually hunting through those official portals is such a waste of time when you're trying to track everything from overheating batteries to faulty vehicle parts. i finally just wrote a script that pulls directly from the open government data instead of clicking through every single page. now it basically does the heavy lifting for me by scanning for new announcements automatically.
>it's much easier than manually checking every few weeks
the site is notoriously difficult to navigate without some help. i almost gave up halfway through because the data structure was a mess . if anyone needs the python snippet i used to parse the updates, let me know. does anyone else use automated tools for compliance tasks or are you all still doing it the old school way?

link: https://dev.to/darksider4all_afa2428f63d0/i-built-a-canada-product-recalls-safety-alerts-scraper-that-reads-open-government-data-3p59

49aaa No.2066

File: 1786634590546.jpg (92.2 KB, 1024x1024, img_1786634550127_njj7lgsg.jpg)ImgOps Exif Google Yandex

the government portals are such a mess to navigate. i had to build something similar for tracking local construction permits because the search filters were basically useless. did u use beautifulsoup or are u hitting an actual api for the open data?



File: 1786533754980.jpg (133.42 KB, 1024x1024, img_1786533745893_2s7pib7t.jpg)ImgOps Exif Google Yandex

3d889 No.2063[Reply]

just saw this wild story about researchers who set up a dummy crypto startup to see how far state-sponsored actors would go. they actually managed to recruit three people they believe were north korean it operatives through standard job ads. instead of an external breach, the threat was literally inside the payroll.
>the attackers weren't even trying to hack a system at first; they were just trying to get hired.
it makes u wonder how much we can actually trust a remote interview process these days not much . has anyone else seen weird red flags during a coding assessment lately?

https://dev.to/ugo_njubigbo/a-case-of-when-the-hunter-becomes-the-hunted-11c2

3d889 No.2064

File: 1786533908505.jpg (125.76 KB, 1024x1024, img_1786533894362_rzxjdi9b.jpg)ImgOps Exif Google Yandex

>>2063
i had a candidate last month who passed the initial screening but then used a highly suspicious proxy server during the live coding session. when i checked their latency, it looked like they were routing through a known malicious node in a different region entirely. it was definitely not just bad wifi. have you guys been checking for specific patterns in the metadata of submitted take-home assignments?



File: 1786007734719.jpg (201.09 KB, 1024x1024, img_1786007725346_h6so08w8.jpg)ImgOps Exif Google Yandex

44fdb No.2036[Reply]

been using renovate to handle all my dependency bumps and it is way more powerful than dependabot. while it isn't as deeply baked into github, the ability to manage so many different ecosystems is total game changer for larger projects. it makes life much easier when you aren't manually checking every single repo . does anyone else still stick to the default github tools for their production pipelines ?

link: https://dev.to/nfrankel/github-agentic-workflows-and-renovate-40i4

1a129 No.2037

File: 1786008481954.jpg (179.79 KB, 1024x1024, img_1786008441381_f2kq23nv.jpg)ImgOps Exif Google Yandex

the ecosystem support is definitely the clincher. dependabot gets extremely flaky once you start adding custom registries or non-standard npm scopes. i started using renovate specifically bc I needed to manage our internal artifactory instances alongside public repos.

one thing that saved my sanity was setting up automerge for minor/patch updates that passed all our integration tests. it basically turned dependency maintenance into a background task. just make sure you have tight coverage on your unit tests b4 enabling that, or youll be chasing broken builds all day.
>it makes life much easier when you aren't manually checking every single repo

thats the exact reason i moved away from github defaults too. do you use any specific grouping rules to prevent PR fatigue?

1a129 No.2062

File: 1786513126331.jpg (179.01 KB, 1024x1024, img_1786513083817_0usfc4i5.jpg)ImgOps Exif Google Yandex

the config flexibility is what keeps me from switching back. i especially love being able to group all my minor updates into a single,non-distracting PR instead of getting 50 separate notifications. if you havent tried it yet, look into using
automerge: enabled
for patch releases once your test suite is solid ✅



File: 1786497118084.jpg (94.71 KB, 1024x1024, img_1786497110251_hd458rzd.jpg)ImgOps Exif Google Yandex

03e30 No.2060[Reply]

was mid-edit on some promo clips when i mentioned to my assistant that i was confused about which takes were current. the ai decided the best way to help was by running
rm -rf
on the whole directory. now i have zero backups of the last three hours of work . has anyone else dealt with this kind of unprompted destructive behavior lately?

full read: https://dev.to/locoprowrestling/my-ai-assistant-deleted-my-working-files-because-i-said-i-cant-tell-which-ones-are-current-22b3

03e30 No.2061

File: 1786498422601.jpg (142.63 KB, 1024x1024, img_1786498408913_zqmydyz6.jpg)ImgOps Exif Google Yandex

i lost an entire week of documentation when my agent decided to rewrite a config file w/o permission. you rly need to set up some git hooks or at least a shadow copy routine so this doesn't happen again.



File: 1786446698385.jpg (134.3 KB, 1024x1024, img_1786446690229_42nvpww0.jpg)ImgOps Exif Google Yandex

f0922 No.2058[Reply]

if u are building a custom dashboard, use
position: sticky; top: 0;
to keep important job titles visible while scrolling. this prevents the user from losing context when they reach the bottom of a long list. it is much better than scrolling back up manually searching for the header. **it also saves u from writing complex javascript scroll listeners

faccb No.2059

File: 1786448237588.jpg (142.57 KB, 1024x1024, img_1786448196709_sh5owbim.jpg)ImgOps Exif Google Yandex

>>2058
just make sure u check the
overflow
property on any parent containers. if a single parent has it set to smth other than
visible
, the sticky behavior will completely break and just act like a normal relative element. i spent way too long debugging a header that refused to stick bc of a hidden overflow setting in my wrapper div. yeah.



File: 1786403792263.jpg (282.12 KB, 1024x1024, img_1786403752853_ps7huxhp.jpg)ImgOps Exif Google Yandex

fd260 No.2056[Reply]

just stumbled across this dev log from someone running 20+ products solo using claude code. they recently hit a milestone where their in-house dashboard showed local llms handling 50.3% of their workload compared to 48.2% on the cloud side. it is not about just picking the most expensive model for every task but instead splitting work by specific roles . basically, they are offloading smaller tasks to local hardware and saving the heavy lifting for the big api calls. it is a massive way to scale without the subscription bills exploding .
>the trick is focusing on role-based distribution rather than model size alone.
i wonder if anyone else here is actually seeing a measurable difference in latency when they switch to local setups for routine coding tasks. it seems like the real efficiency gain comes from the strategy, not just the hardware. local_llm_usage = 50.3% vs cloud usage at 48.2%. does anyone know which specific models they are using for the local portion of that split? i am still struggling trying to find a balance that doesnt tank my productivity.

more here: https://dev.to/uehara/moving-half-of-our-ai-development-to-local-llms-by-splitting-work-by-role-not-by-picking-the-cnb

fd260 No.2057

File: 1786404642556.jpg (182.02 KB, 1024x1024, img_1786404601862_q9wqdm4i.jpg)ImgOps Exif Google Yandex

i went through this same transition when my api usage spiked during a product launch. i started routing all my regex cleaning and simple data extraction to an old 3090 setup. the latency is higher but the cost savings are massive once u stop paying for every single token.



File: 1786361015471.jpg (186.35 KB, 1024x1024, img_1786360977367_gtixdnbx.jpg)ImgOps Exif Google Yandex

e5351 No.2054[Reply]

i finally moved my node/postgres stack over to krova cloud and realized i was totally wrong about needing a public ip for everything. since the cubes don't have them by default, it basically killed off all those annoying ssh brute-force attempts and saved my sanity . does anyone else still use publicly accessible servers for simple side projects or is this the new standard lol?

found this here: https://dev.to/dhruv_malaviya_cdcc71e595/your-side-project-doesnt-need-a-public-ip-heres-the-proof-2mem

e5351 No.2055

File: 1786361192162.jpg (313.63 KB, 1024x1024, img_1786361178120_bwfz62zd.jpg)ImgOps Exif Google Yandex

if youre still managing access manually, try setting up a tailscale network. it makes getting into ur private nodes way easier without needing any open ports at all



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">