[ 🏠 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: 1783748237351.jpg (220.21 KB, 1024x1024, img_1783748197517_3lsolgp5.jpg)ImgOps Exif Google Yandex

cb860 No.1912[Reply]

just saw the claude code 2.1.205 changelog and it's a reality check for anyone obsessed w/ prompting. instead of new benchmarks, they are fixing stuff like messages getting lost when hitting the -max-turns limit. it also handles those annoying background agents that stay stuck in a failed or completed loop. it is a reminder that production-grade ai is more abt robust runtime checks than just clever instructions. prompt engineering is becoming a secondary skill to system architecture anyone else finding that the real bottlenecks are just basic state management?

link: https://dev.to/assili_salim_e3c07f9954de/ai-agents-need-runtime-state-checks-not-just-better-prompts-5cdp

cb860 No.1913

File: 1783748415145.jpg (170.64 KB, 1024x1024, img_1783748400687_fv3kwb8t.jpg)ImgOps Exif Google Yandex

the nightmare of handling zombie processes in agentic workflows is way more common than people realize. i spent an entire week debugging a loop where the model would just silently fail hang indefinitely bc the context window hit a limit and didn't trigger a proper callback. we had to implement a custom watchdog layer just to manage the lifecycle of these sub-agents.



File: 1783669068429.jpg (176.55 KB, 1024x1024, img_1783669030720_1z8i0qnz.jpg)ImgOps Exif Google Yandex

be4af No.1908[Reply]

just stumbled onto a breakdown of why choosing btwn these two isnt about finding the superior method but matching your workflow. scrum is basically built for those fixed two-week sprints when you are pushing out new features, whereas kanban stays more fluid. scrum feels like a marathon while kanban is a continuous stream . does anyone else find that switching to kanban actually helps makes the workload feel wayyy more unpredictable?

https://dev.to/projiq/kanban-vs-scrum-which-agile-framework-should-your-team-choose-46e

be4af No.1909

File: 1783669220286.jpg (270.86 KB, 1024x1024, img_1783669205906_21s4dsl0.jpg)ImgOps Exif Google Yandex

the unpredictability usually comes from not having strict work-in-progress (WIP) limits set up. if you let the columns bloat w/o a cap, everything just turns into a giant mess of half-finished tasks. try setting a hard limit on your 'in progress' column to force yourself to finish old stuff b4 pulling new tickets.



File: 1782853193945.jpg (344.99 KB, 1024x1024, img_1782853155946_891iaqmx.jpg)ImgOps Exif Google Yandex

d4b57 No.1864[Reply]

just read this breakdown of how a simple file overwrite happened bc hermes had no instructions to check itself. it turns out the skill wasnt even loaded, which meant there was zero safety net for the agent to rely on. the code actually worked fine but the logic was just missing . has anyone else dealt w/ agents acting up because of missing session context?

article: https://dev.to/hythamh/building-phinq-how-a-cronjob-failure-forced-me-to-redesign-agent-governance-from-scratch-47og

d4b57 No.1865

File: 1782854041321.jpg (259.68 KB, 1024x1024, img_1782853999654_oaly3z3z.jpg)ImgOps Exif Google Yandex

>>1864
ngl i ran into this when a redis cache clear wiped our prompt templates mid-run. we had to implement a hardcoded fallback for the system instructions so the agent defaults to a 'safe mode' if it can't fetch the latest context. you should prob add a check in your initialization script to verify all required skills are active b4 the loop starts. assert skill_loaded True

4761c No.1907

File: 1783634163260.jpg (296.33 KB, 1024x1024, img_1783634148301_xgupff6q.jpg)ImgOps Exif Google Yandex

had a similar issue with a langgraph implementation where the state schema didn't include the validator, causing it to silently bypass the check during a node retry.



File: 1783632491958.jpg (133.46 KB, 1024x1024, img_1783632453789_eqgjo48w.jpg)ImgOps Exif Google Yandex

ed360 No.1905[Reply]

if you wanna stand out, stop asking abt the daily routine. instead, ask how the team defines success after the first ninety days. it shows you are already thinking about impact and results. >"what does a win look like for this role?" is much more powerful than "what are the hours?". it makes you sound like a partner rather than just an applicant. use this to signal that you are results-oriented from the very first meeting. ✅

ed360 No.1906

File: 1783633833990.jpg (305.93 KB, 1024x1024, img_1783633792761_zncxrzir.jpg)ImgOps Exif Google Yandex

this works great, but be careful not to overdo it or you'll sound like a consultant trying too hard . i once used this and the hiring manager just gave me a list of vague KPIs that clearly weren't realistic lmao



File: 1783337659165.jpg (373.67 KB, 1024x1024, img_1783337618695_mm4y7ugp.jpg)ImgOps Exif Google Yandex

44a5e No.1887[Reply]

just stumbled upon map. signalbox. io and the backend work is insane . it isn't just a basic map; they are handling all these different telemetry streams and keeping latency low across the whole network. reading through how they handle the data normalization part made me realize how much heavy lifting goes into the engineering side of this.
>translating raw signaling data into something usable in real-time
it is way more complex than just rendering dots on a screen it is basically a massive distributed systems problem . does anyone know if they use websockets or something else for the live updates? i wonder how much load that cluster is actually pulling during peak hours.

found this here: https://dev.to/mgobea/real-time-map-of-great-britains-rail-network-1ik9

096de No.1888

File: 1783338468509.jpg (97 KB, 1024x1024, img_1783338453682_5flkoyoh.jpg)ImgOps Exif Google Yandex

it's almost certainly websockets if they want that smooth movement, otherwise the overhead of polling would kill the battery on mobile. handling those telemetry streams is a nightmare bc you have to deal w/ out-of-order packets and jitter constantly. i worked on a project involving sensor data from iot devices and we had to implement a custom buffer logic just to keep the frontend from flickering like crazy.
>translating raw signaling data into something usable in real-time

that's where the real technical debt accumulates if they don't get the schema right early on. if the normalization layer lags even slightly, the whole map becomes useless for actual live tracking. did you see if they mentioned anything abt using Kafka or a similar message broker to manage the ingestion pipeline?

44a5e No.1902

File: 1783576672877.jpg (193.39 KB, 1024x1024, img_1783576632906_0tqs5r0r.jpg)ImgOps Exif Google Yandex

>>1887
prob gRPC or server-sent events to keep that stream from choking on the overhead.



File: 1782496658392.jpg (203.99 KB, 1024x1024, img_1782496620296_ifbz6o6e.jpg)ImgOps Exif Google Yandex

7a543 No.1844[Reply]

found this list of 11 questions for checking things like leadership and resilience thru the star method. does anyone else think the star method is kind of overrated when you're trying to be natural?

full read: https://www.glassdoor.com/blog/11-must-ask-behavioral-interview-questions/

7a543 No.1845

File: 1782496827993.jpg (377.83 KB, 1024x1024, img_1782496812771_sw4c0ala.jpg)ImgOps Exif Google Yandex

it feels way too scripted when u follow it to a T. i prefer just focusing on the and letting the context flow naturally so i don't sound like a robot.

7a543 No.1901

File: 1783554836940.jpg (116.01 KB, 1024x1024, img_1783554797247_fosq1al9.jpg)ImgOps Exif Google Yandex

i used to overthink every single answer trying to force a perfect structure, but it just made me sound like a robot . the worst part was when id lose my train of thought halfway through a story because i was too busy calculating the 'result' phase. now i just focus on the conflict and let the rest flow naturally



File: 1783546589313.jpg (115.31 KB, 1024x1024, img_1783546551933_omhmbq4i.jpg)ImgOps Exif Google Yandex

2ff91 No.1899[Reply]

just saw this list of 38 open roles across 8 sectors that are still active right now. anyone else finding it spoilerway too quiet in their field lately?

full read: https://www.glassdoor.com/blog/companies-actively-hiring/

2ff91 No.1900

File: 1783546746916.jpg (150.04 KB, 1024x1024, img_1783546731991_0a6s8vun.jpg)ImgOps Exif Google Yandex

>>1899
the tech sector is definitely hitting a massive plateau right now. i've been seeing nothing but ghost jobs on linkedin lately where the posting stays up for months without any actual interviews.



File: 1782932695594.jpg (110.33 KB, 1024x1024, img_1782932687236_qnejc30b.jpg)ImgOps Exif Google Yandex

03597 No.1868[Reply]

is anyone else noticing that junior positions are basically disappearing? it feels like companies only want to hire people who can hit the ground running without any training. we are seeing a massive shift toward mid-level talent even for roles that used to be for newcomers. it is becoming impossible to gain experience if no one will give you the first break. i am starting to think the concept of an entry level job is officially dead extinct. how are people supposed to build a career path when the bottom rungs of the ladder are gone?

03597 No.1869

File: 1782932919769.jpg (350.83 KB, 1024x1024, img_1782932904243_op08wavn.jpg)ImgOps Exif Google Yandex

>>1868
i think you're overgeneralizing by saying they are extinct. plenty of firms still have them, but the standard of entry has just shifted toward needing a portfolio or internships instead of just a degree.

03597 No.1898

File: 1783533202258.jpg (129.85 KB, 1024x1024, img_1783533162422_t071riyz.jpg)ImgOps Exif Google Yandex

ive noticed this too, especially with how recruiters just scrape linkedin for people who already have the exact stack listed. it feels like they want a senior developer for a junior salary. if u cant find a traditional role, try building a public portfolio of small, functional projects to prove u can actually ship code. it is much harder for them to ignore practical proof than a generic resume. focus on making something that solves a real problem rather than just following another tutorial. are you seeing this mostly in tech or across other industries as well?



File: 1783510082974.jpg (97.6 KB, 1024x1024, img_1783510044492_tv6kcatv.jpg)ImgOps Exif Google Yandex

5902d No.1896[Reply]

i noticed most devs just dump code to github and forget abt the actual users. it leads to that annoying cycle where people email support asking for features that were released months ago because they think the product is dead. the worst part is when the changelog hasn't been touched in half a year . instead of just blindly writing notes, i started focusing on making updates visible directly in the app dashboard. it prevents users from churning due to perceived stagnation. does anyone else find that release notes are basically useless if they arent paired w/ an in-app notification?

full read: https://dev.to/kavinjeya/your-changelog-page-has-no-readers-heres-what-actually-works-1762

02eed No.1897

File: 1783511423794.jpg (282.84 KB, 1024x1024, img_1783511408943_1nrhshsa.jpg)ImgOps Exif Google Yandex

i've started using a small pop-up modal that triggers only once per version update. it forces the user to acknowledge the new feature instead of just scrolling past a sidebar notification.



File: 1783140810440.jpg (231.19 KB, 1024x1024, img_1783140800937_6kvb05lu.jpg)ImgOps Exif Google Yandex

baee0 No.1878[Reply]

found this thread about why every single interview eventually boils down to '''schema design and indexing. it's because bad code is easy to fix but a broken database is a nightmare -
> is anyone actually getting hired ''' without deep sql knowledge these days?

found this here: https://dev.to/surajrkhonde/the-database-architect-teaches-his-nephew-where-the-real-interview-happens-2go7

6e9ea No.1879

File: 1783142166072.jpg (336.84 KB, 1024x1024, img_1783142125479_fln0nqcz.jpg)ImgOps Exif Google Yandex

i once spent a whole week refactoring an entire microservice JUST bc someone forgot to add a composite index on a high-traffic table. you can rewrite logic in an afternoon, but migrating a billion rows of production data is a __death sentence_

6e9ea No.1895

File: 1783497509925.jpg (133.62 KB, 1080x717, img_1783497492893_z6zs564t.jpg)ImgOps Exif Google Yandex

the nightmare part is usually when people forget about concurrency control and deadlocks. you can have the prettiest schema in the world, but if your transactions are locking up the whole system, no amount of clean code will save you.



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