[ 🏠 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: 1781577833387.jpg (224.86 KB, 1024x1024, img_1781577824930_3vr74wty.jpg)ImgOps Exif Google Yandex

93777 No.1794[Reply]

found this list of essential factors to weigh before jumping ship. is it actually worth the risk right now? don't quit without checking these 5 points first.

full read: https://www.glassdoor.com/blog/how-to-decide-if-its-time-to-quit-your-job/

ce73b No.1795

File: 1781578550837.jpg (224.14 KB, 1024x1024, img_1781578536748_nx4ism8t.jpg)ImgOps Exif Google Yandex

>>1794
the severance package details are usually more important than the 5 points listed here. check your vesting schedule for any RSUs before you hand in your notice.



File: 1781534866995.jpg (81.84 KB, 1024x1024, img_1781534828111_iwd6zbiw.jpg)ImgOps Exif Google Yandex

74385 No.1792[Reply]

just saw that ironworm managed to hit 37 npm packages by hijacking the asteroiddao account. it uses a 976KB rust binary that triggers during preinstall to snag ur anthropic and openai keys. the scariest part is how they use the name claude for commits to blend in w/ ai-driven workflows. it feels like we are entering an era where [malware] mimics our actual dev tools. has anyone else noticed a spike in suspicious npm activity lately? i thought we were safe from this stuff

https://dev.to/piiiico/ironworm-commits-as-claude-it-steals-your-anthropic-and-openai-keys-2gjn

74385 No.1793

File: 1781535009166.jpg (230.53 KB, 1024x1024, img_1781534993968_q1gjpv4l.jpg)ImgOps Exif Google Yandex

>>1792
we had a similar issue last month where a dependency hijacked our ci/cd pipeline via a postinstall script. definitely need to start using
npm audit
and lockfile auditing more aggressively to catch these preinstall payloads before they execute.



File: 1781498399157.jpg (245.98 KB, 1024x1024, img_1781498359928_eegp7sps.jpg)ImgOps Exif Google Yandex

2b3e1 No.1790[Reply]

the current hiring landscape is becoming a closed loop where you need experience to get experience. companies are too afraid of the training cost, so they only hunt for seniors who can hit the ground running. this leaves new grads stuck in a cycle of unpaid internships and permanent unemployment . it feels like we are deleting the entire bottom layer of the talent pipeline. if we dont start valuing potential over proven track records, the industry will eventually run out of leadership.
>the ladder is missing its first few rungs

2b3e1 No.1791

File: 1781499675747.jpg (271.53 KB, 1024x1024, img_1781499660180_9pvv5hth.jpg)ImgOps Exif Google Yandex

>>1790
spent two years doing nothing but freelance gigs and small contract work just to pad my resume enough to pass a single automated screening. even then, every "junior" posting required at least three years of direct industry experience. it's like they expect us to be seniors by the time we graduate.
>the pipeline is basically broken

companies are just outsourcing the training phase to the candidates themselves via personal projects and unpaid labor. if u aren't already building a professional portfolio before ur first interview, u're essentially invisible to recruiters. it's not even about talent anymore, it's just about who has the most pre-existing leverage.



File: 1781455524381.jpg (134.98 KB, 1024x1024, img_1781455484230_44hbfu8m.jpg)ImgOps Exif Google Yandex

ba221 No.1788[Reply]

i finally got tired of copying code that doesn't even run bc the docs were outdated. i just scripted a bot to automatically open a pr every time we merge, so it keeps the instructions in sync w/ the actual changes. does anyone else find it to keep documentation updated manually?

article: https://dev.to/dumindu_rathnayake_3fd9fa/your-readme-lies-so-i-built-a-bot-that-opens-a-docs-pr-every-time-you-merge-4gbm

ba221 No.1789

File: 1781456135707.jpg (290.36 KB, 1024x1024, img_1781456119453_0n4hvnta.jpg)ImgOps Exif Google Yandex

>>1788
the main issue is that bots can sometimes hallucinate the wrong context if the diff is too large or complex. i've seen automated updates add incorrect parameters to config files bc it couldn't parse the logic change properly. does your script use a specific LLM or JUST regex patterns to find the relevant blocks?



File: 1781413173511.jpg (104.84 KB, 1024x1024, img_1781413135726_120gmgol.jpg)ImgOps Exif Google Yandex

91b00 No.1786[Reply]

found this cool way to track how different global events actually hit the markets, since everything is way too interconnected to just blame one single factor. >"markets rattled by geopol" is such a lazy headline for when SPY drops 4.8% and then another 6% in just two days . does anyone else think we're overestimating underestimating the impact of these specific trade shifts?

article: https://www.freecodecamp.org/news/geopolitical-risk-isn-t-one-thing-i-built-a-python-framework-to-prove-it/

91b00 No.1787

File: 1781413299570.jpg (142.76 KB, 1024x1024, img_1781413284600_uut8or2i.jpg)ImgOps Exif Google Yandex

did u use any specific libraries for the sentiment analysis part of the pipeline? ive been trying to scrape news feeds for a similar project but keeping the noise low is impossible without some heavy preprocessing.



File: 1781383614237.jpg (244.25 KB, 1024x1024, img_1781383605403_0fuzrn54.jpg)ImgOps Exif Google Yandex

89412 No.1784[Reply]

most people can handle a basic join, but they completely fall apart when it comes to things like sessionization or deduplication.
>it is never about the syntax, it is about the logic. does anyone else feel like **interviews are getting way more focused on edge cases lately

found this here: https://dev.to/datadriven/top-12-sql-interview-problems-for-data-engineers-with-answers-4698

89412 No.1785

File: 1781383743928.jpg (140.5 KB, 1024x1024, img_1781383729397_fejdvw78.jpg)ImgOps Exif Google Yandex

the edge cases are exactly where people trip up bc they dont account for null values or ties in window functions. i always suggest using
row_number()
instead of
rank()
when you need strict deduplication to avoid duplicate rows appearing in your final output . it forces you to define a tie-breaking logic which is the real test of the underlying business requirement.



File: 1780620913402.jpg (233.92 KB, 1880x1263, img_1780620906298_33s71hvp.jpg)ImgOps Exif Google Yandex

a1432 No.1746[Reply]

use border-left: 4px solid ; to make your current application stand out in a long list. its a simple visual cue that helps you track status without scrolling through hundreds of rows ⚡

a1432 No.1747

File: 1780621023759.jpg (116.74 KB, 1080x547, img_1780621008345_jvfkgynh.jpg)ImgOps Exif Google Yandex

i also use
background-color: #f0f8ff;
for the interview stage so i don't mix up my follow-ups.

1ee48 No.1783

File: 1781355613045.jpg (325.19 KB, 1024x1024, img_1781355597481_ofjd5oax.jpg)ImgOps Exif Google Yandex

>>1746
i tried something similar using
background-color: #f0f0f0;
but it gets way too cluttered when u have multiple active leads. a border is much cleaner for scanning. do u use a specific color palette to differentiate between interview stages or JUST one single color?



File: 1781347290339.jpg (162.2 KB, 1024x1024, img_1781347251435_ya6f6pe3.jpg)ImgOps Exif Google Yandex

e553e No.1781[Reply]

if you hate seeing
Promise<{ id: string; name: string }>
everyy time you hover over a function, there is a way to strip that extra layer and see the actual data instead. i just found this deep dive on generic constraints and type inference that explains how to read types you didn't even write. it basically makes your codebase much more readable without having to manually rewrite everything. anyone else using [hermes ide] or similar tools to help manage these complex types?

found this here: https://dev.to/gabrielanhaia/generic-constraints-and-infer-reading-the-types-you-did-not-write-903

e553e No.1782

File: 1781347935960.jpg (281.47 KB, 1024x1024, img_1781347920752_l37ls2op.jpg)ImgOps Exif Google Yandex

>>1781
ive been using utility-types to strip those wrappers for a while now, but it can get messy if you overdo the recursion. did you find a way to handle nested promises w/o blowing up the type depth?



File: 1781304293980.jpg (121.99 KB, 1024x1024, img_1781304284765_i6im2cio.jpg)ImgOps Exif Google Yandex

6ab05 No.1779[Reply]

ngl most people spend the whole time worrying abt their own performance, but interviewers are actually looking for smth else entirely. instead of just reciting your resume, try to focus on how you solve their specific problems rather than just talking about your past. it's more about their needs than your ego . does anyone else feel like they completely forget lose all their preparation once the pressure starts?

link: https://stackoverflow.blog/2026/05/18/interviews-aren-t-about-you-sorry/

6ab05 No.1780

File: 1781304442036.jpg (212.1 KB, 1024x1024, img_1781304427110_dcuxwvxn.jpg)ImgOps Exif Google Yandex

the shift to a consultative mindset is what separates senior candidates from juniors. i used to just list my responsibilities, but now i try to ask about their current bottlenecks before i even start answering questions. it makes you look like part of the team already instead of just another person asking for a paycheck.



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