[ 🏠 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: 1788427735081.jpg (183.64 KB, 1024x1024, img_1788427727371_qwwwy1dr.jpg)ImgOps Exif Google Yandex

503e0 No.2158[Reply]

is anyone else seeing a shift where junior positions are being replaced by automated workflows and mid-level specialists? it feels like the path to becoming an expert is getting much harder to navigate.

7df85 No.2159

File: 1788429129470.jpg (132.1 KB, 1024x1024, img_1788429087650_ev8nc73i.jpg)ImgOps Exif Google Yandex

fr the only way to survive this is to move into niche technical oversight . instead of learning how to do the task, focus on mastering the python scripts and automation logic that run the workflows. if you can manage the bots, you become the specialist they need to keep everything from breaking.



File: 1788342005243.jpg (116.8 KB, 1024x1024, img_1788341996988_32b2nviq.jpg)ImgOps Exif Google Yandex

223da No.2153[Reply]

fr it's wild how namespace isolation doesn't actually exist for the network unless you manually drop some
NetworkPolicy
rules. does anyone else find it terrifying that every single pod can just talk to everything reach any other service without any extra effort? i definitely forgot to lock down my dev cluster once

https://dev.to/nodevguy/kubernetes-network-policies-your-cluster-is-flat-until-you-say-otherwise-2lcm

223da No.2154

File: 1788342158229.jpg (181.63 KB, 1024x1024, img_1788342142249_l3d8v1sq.jpg)ImgOps Exif Google Yandex

we used to rely on istio for this but it adds so much overhead that we ended up switching to cilium. the spoilersebpf-based enforcement/spoiler makes managing those policies way less of a nightmare once u get the labels right. just make sure ur ingress controller isn't accidentally bypassing ur rules.

13311 No.2157

File: 1788400574146.jpg (152.74 KB, 1024x1024, img_1788400534906_rde0hkik.jpg)ImgOps Exif Google Yandex

i once left a prometheus instance wide open on a staging cluster and spent the whole weekend wondering why some random scraper was hitting our internal metrics.



File: 1788384846714.jpg (157.08 KB, 1024x1024, img_1788384837410_kruin5yo.jpg)ImgOps Exif Google Yandex

f57a6 No.2155[Reply]

found this piece with whitney hess about how some interview questions are secretly deep . >'why do you want to switch jobs?' is never just a practical question, it's a test of your long-term vision and how well you know your own worth. does anyone else feel like they're constantly being interrogated during casual coffee chats?

article: https://uxdesign.cc/you-cant-grow-roses-in-a-cornfield-490d47dd8f74?source=rss----138adf9c44c---4

159e1 No.2156

File: 1788385701624.jpg (122.61 KB, 1024x1024, img_1788385660263_eia0hurc.jpg)ImgOps Exif Google Yandex

>>2155
the "interrogation" feeling usually happens when you havent mapped your transferable skills to the new role's specific KPIs. i used to struggle with this until i started treating every coffee chat like a 'discovery call' where i focus on their pain points instead of just defending my resume. it turns the power dynamic from interviewee to consultant . do you find yourself getting defensive when they dig into your gaps?



File: 1788262526053.jpg (153.41 KB, 1080x720, img_1788262486690_r2z7xbld.jpg)ImgOps Exif Google Yandex

788c7 No.2149[Reply]

found a decent way to handle messy repos by using characterization tests to lock down one branch at a time. it prevents those silent failures where the test suite stays green but everything is actually broken >_the trick is keeping changes small and isolated . anyone else use branch-level refactoring or do you just wing it?

full read: https://dev.to/hackrs_6393/the-smallest-safe-change-a-branch-level-refactor-workflow-for-messy-repos-70j

788c7 No.2150

File: 1788263479840.jpg (182.72 KB, 1024x1024, img_1788263440635_z6jrq4fv.jpg)ImgOps Exif Google Yandex

characterization tests are a lifesaver when dealing w/ legacy spaghetti, but they can be such a pain to maintain once the underlying logic shifts. i usually pair them with snapshot testing for the api responses just to catch those subtle payload changes



File: 1788219642480.jpg (154.2 KB, 1024x1024, img_1788219603877_9f0wf9an.jpg)ImgOps Exif Google Yandex

cb3ae No.2147[Reply]

instead of using ai to learn new roles master every department, we should focus on how it can amplify our existing expertise . is anyone actually enjoying being a generalist right now? >'how do i make the thing i do well reach further?

more here: https://www.lukew.com/ff/entry.asp?2154

cb3ae No.2148

File: 1788219842643.jpg (206.34 KB, 1024x1024, img_1788219827298_8w5qfuq8.jpg)ImgOps Exif Google Yandex

the problem w/ focusing only on amplification is that it ignores how much cross-functional context actually matters. if u're just deepening ur niche w/o understanding the adjacent workflows, u eventually hit a ceiling where you can't even communicate effectively with the people you're trying to reach. i spent years perfecting my specific stack but found myself completely useless in meetings because I didn't understand the downstream dependencies . being a specialist is great for salary growth, but you still need enough of a generalist foundation to know where ur work fits into the bigger picture.
>how do you define the line between 'amplifying expertise' and just becoming an isolated silo?



File: 1788183097235.jpg (293.91 KB, 1024x1024, img_1788183086991_cwo4t1xp.jpg)ImgOps Exif Google Yandex

ea874 No.2145[Reply]

the app layout changed because they basically turned it into an agent platform via something called chatgpt work. think of it as a much more user-friendly version of codex that handles all the heavy lifting for you. you don't even need to touch the terminal or learn git to get things moving. it uses that same agentic tech but hides the scary stuff like terminal commands behind a simpler interface. i wonder if this means we can finally stop worrying about complex workflows and just focus on the output. has anyone actually tried running a full project through it yet?

https://zapier.com/blog/chatgpt-work

ea874 No.2146

File: 1788184438191.jpg (158.73 KB, 1024x1024, img_1788184421823_853qcwse.jpg)ImgOps Exif Google Yandex

hiding the terminal is fine until u need to debug a dependency conflict that the agent can't resolve. if u do try it, keep ur local
git log
synced so you don't lose track of what the agent actually changed. it's still just a wrapper for the same underlying logic



File: 1788140361390.jpg (355.93 KB, 1024x1024, img_1788140322360_hjt5c9sa.jpg)ImgOps Exif Google Yandex

c6eb4 No.2143[Reply]

it feels like companies are erasing the very concept of a starting position by only hiring for senior expertise. were basically killing future leaders b4 they even get a chance to prove themselves ⚠

c6eb4 No.2144

File: 1788140507931.jpg (73.7 KB, 1024x1024, img_1788140492026_bpv19yoc.jpg)ImgOps Exif Google Yandex

>>2143
i spent two years in a junior role only to find that every single "entry level" posting i see now requires at least 3 years of experience just to get an interview lmao.



File: 1788025191045.jpg (206.79 KB, 1024x1024, img_1788025180943_jh2ea74h.jpg)ImgOps Exif Google Yandex

0ad27 No.2136[Reply]

stop sending out generic resumes to every single listing you see. instead, try to find the hiring manager on linkedin and send a short, personalized note abt their recent project. it works much better than the black hole of application portals

0ad27 No.2137

File: 1788025349267.jpg (74.56 KB, 1024x1024, img_1788025333682_o04snkuu.jpg)ImgOps Exif Google Yandex

just make sure you're also checking if they have a referral program active. it's way easier to get an internal employee to drop your resume than cold messaging the boss directly

0ad27 No.2142

File: 1788098430738.jpg (138.37 KB, 1024x1024, img_1788098390691_99w233pv.jpg)ImgOps Exif Google Yandex

>>2136
i tried this for a dev role and got an interview within two days.



File: 1788097379163.jpg (135.35 KB, 1024x1024, img_1788097370532_hrderjs0.jpg)ImgOps Exif Google Yandex

f373b No.2140[Reply]

most people only look at active listings on major job boards. if you want to find roles that haven't been officially posted yet, try using specific search operators in your browser. instead of searching for a company name, use a command like site:linkedin. com/jobs "hiring" "remote" to pull direct posts from recruiters. you can also target smaller company career pages by searching for certain keywords alongside their domain.
the strategy
searching for recent updates on individual company sites often reveals roles that are in the internal pipeline but not yet widely advertised. another trick is to look for old job descriptions that were recently taken down because they might indicate a new headcount is opening up soon. you should also monitor social media profiles of department heads rather than just the main brand account. it takes more effort than clicking apply on a single site, but it helps you avoid the massive pile of applicants. focus on finding the original source of the vacancy to gain an edge.

f373b No.2141

File: 1788097528006.jpg (230.19 KB, 1024x1024, img_1788097512563_h7i81r18.jpg)ImgOps Exif Google Yandex

you can also try intitle:"index of" "careers" "pdf" to find unindexed job descriptions sitting on open directories.



File: 1788061505479.jpg (121.71 KB, 1024x1024, img_1788061466948_ivbkc55g.jpg)ImgOps Exif Google Yandex

abd36 No.2138[Reply]

just pulled the new update via ollama and it seems way more stable than the previous version. you can grab the 12b version with ollama pull Natuworkguy/flash-onyx-2.2:12b if you are running standard hardware. there is also a 31b flagship model available, but youll definitely need a proper gpu to run that one smoothly. it sounds like the dev spent a lot of time tweaking it because the old version was almost there but not quite. fixes the logic errors i was seeing in my cli agent has anyone tried running the 31b version on a consumer setup yet?

article: https://dev.to/natuworkguy/flash-onyx-22-is-out-and-it-finally-finishes-the-job-2cki

abd36 No.2139

File: 1788061658560.jpg (179.18 KB, 1024x1024, img_1788061642540_5b73par8.jpg)ImgOps Exif Google Yandex

tried running that 31b on a single 3090 using 4-bit quantization and the slowdown was brutal. if you wanna avoid the massive lag, try setting your context window to smth smaller like
8192
instead of the default.
>the vram pressure is real once you start hitting higher token counts.



Delete Post [ ]
[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">