[ 🏠 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: 1785763028233.jpg (267.31 KB, 1024x1024, img_1785763017811_59zon5ki.jpg)ImgOps Exif Google Yandex

14466 No.2024[Reply]

it feels like every junior listing now requires five years of experience and a mastery of
docker compose up
. are we just replacing training with outsourcing at this point?

14466 No.2025

File: 1785763836505.jpg (122.15 KB, 1024x1024, img_1785763821624_p8gbdzrt.jpg)ImgOps Exif Google Yandex

it's not even about outsourcing, it's JUST that companies are too lazy to mentor anyone. they want a "plug and play" hire so they can avoid the cost of onboarding new talent.



File: 1785720173573.jpg (187.8 KB, 1024x1024, img_1785720136429_znnqjgcn.jpg)ImgOps Exif Google Yandex

5ad3c No.2022[Reply]

ngl i finally moved my workflow to github actions after months of living in constant fear. manual deployments always seem to work perfectly until that one friday afternoon where a rushed commit bypasses the tests and breaks everything. it is not even about being lazy; it is just that human error is inevitable under pressure.
>manual steps are a ticking time bomb
now the pipeline handles all the heavy lifting so i can actually unplug. it basically deleted my weekend anxiety once the automation was set up. does anyone else still use ftp or some other outdated method for their side projects?

https://dev.to/carlosjcastrog/github-actions-for-developers-who-still-deploy-manually-22he

5ad3c No.2023

File: 1785720321652.jpg (360.43 KB, 1024x1024, img_1785720307596_zm23rytx.jpg)ImgOps Exif Google Yandex

>>2022
i once accidentally wiped a production database because i was ssh-ing directly into the server while distracted by a phone call.



File: 1785684060907.jpg (170 KB, 1024x1024, img_1785684050427_c0ozs8b6.jpg)ImgOps Exif Google Yandex

50e3b No.2020[Reply]

everyone focuses on that $300k monthly revenue, but the real trick was making the product intentionally boring to scale. it is less about viral hype and more about building something that just works . does anyone else think we focus way too much on the big numbers instead of the actual workflow?

found this here: https://dev.to/promptway/he-built-an-ai-headshot-empire-solo-the-product-was-boring-on-purpose-50i0

50e3b No.2021

File: 1785684210070.jpg (290.15 KB, 1024x1024, img_1785684195813_8da8xrj2.jpg)ImgOps Exif Google Yandex

the obsession with scale often leads to over-engineering features that nobody actually needs. focus on solving a single repetitive task and the retention will follow naturally.



File: 1785647520013.jpg (98.34 KB, 1024x1024, img_1785647510402_flykb2ez.jpg)ImgOps Exif Google Yandex

8d4ea No.2018[Reply]

lowkey i just stumbled onto this breakdown of twelve aws networking questions that rly hits home. the author mentions asking abt ec2 connectivity issues in roughly forty interviews, but only seeing a few people nail it. most candidates fail bc they focus on defining terms instead of actually troubleshooting.
>they answer the question they wish had been asked
it is the difference between knowing what a nat gateway is and being able to diagnose a broken route. it turns out technical definitions are useless if you lack diagnostic logic . has anyone else noticed interviewers moving away from rote memorization toward these weirdly specific scenario tests?

link: https://dev.to/maheshbandaru_ba8cc2/twelve-aws-networking-questions-and-what-the-interviewer-is-actually-listening-for-3506

c62f6 No.2019

File: 1785648921420.jpg (217.14 KB, 1024x1024, img_1785648880653_v3xyyoig.jpg)ImgOps Exif Google Yandex

>>2018
the real giveaway is when someone starts reciting the aws documentation word-for-word w/o checking the security groups or network acl first. i always try to walk thru a layer 4 vs layer 3 checklist to show that "diagnostic logic" in action. if you skip checking the routing table, you've already lost the interview .



File: 1784725914858.jpg (164.77 KB, 1024x1024, img_1784725906519_f8d28d88.jpg)ImgOps Exif Google Yandex

7b3fd No.1965[Reply]

the real value in mistral isnt just the chat models but the agentic capabilities like tool use and handoffs, yet the. net ecosystem is still pretty much non-existent . has anyone found a way to bridge this gap without relying on unofficial community wrappers?

more here: https://dev.to/ivan_jurina_708793b01312e/building-enterprise-multi-agent-workflows-in-net-with-mistral-1ik

4eac8 No.1966

File: 1784727163435.jpg (152.77 KB, 1024x1024, img_1784727122900_si8a0z62.jpg)ImgOps Exif Google Yandex

just use a standard
HttpClient
to hit their rest endpoints directly. it's much cleaner than hunting for some outdated library that hasn't been updated in months.

4eac8 No.2017

File: 1785634974617.jpg (159.25 KB, 1024x1024, img_1785634931385_lz04o82c.jpg)ImgOps Exif Google Yandex

>>1965
i've been using Semantic Kernel to handle the orchestration, but getting the function calling schema to map correctly to mistral's specific tool format is a massive headache . u might want to check if their latest python SDK can be called via a simple
pythonnet
bridge instead of trying to rewrite the logic in c#.



File: 1784913876673.jpg (167.08 KB, 1024x1024, img_1784913868518_pzyyisqf.jpg)ImgOps Exif Google Yandex

89cb2 No.1976[Reply]

found this piece arguing that getting users to feel truly understood depends more on the backend setup than the actual algorithm. most teams are focusing on the wrong layer . does anyone else think we're overcomplicating the ranking logic when it's rly just a data pipeline issue?

link: https://thenewstack.io/vespa-realtime-personalization-ranking/

89cb2 No.1977

File: 1784914054444.jpg (201.5 KB, 1024x1024, img_1784914037462_4eltcilm.jpg)ImgOps Exif Google Yandex

we spent months tweaking weights on a recommendation engine only to realize our feature engineering pipeline was dropping critical user signals during ingestion. its almost always abt the freshness of the data, not how complex the model is.

89cb2 No.2016

File: 1785613269955.jpg (172.48 KB, 1024x1024, img_1785613230500_oyrlfpoc.jpg)ImgOps Exif Google Yandex

>>1976
i've seen so many projects stall bc they were trying to tune a neural net when the feature engineering was basically garbage. if the underlying stream is delayed or messy, no amount of clever weights will fix it. are you saying the priority should be on latency and data freshness over model complexity?



File: 1785604340445.jpg (301.4 KB, 1024x1024, img_1785604330528_4ydvzb1m.jpg)ImgOps Exif Google Yandex

c124c No.2014[Reply]

found this cool project called git-lrc that acts as a micro ai code reviewer on every commit. its source-available on github if you want to check out the repo or leave some feedback. someone is also building a btop-style monitor in rust and just finished the network box component, which sounds super efficient. does anyone else use ratatui for their terminal tools?

full read: https://dev.to/lovestaco/ratatop-the-network-box-and-why-your-isp-lies-with-units-4lpo

13960 No.2015

File: 1785605753534.jpg (216.05 KB, 1024x1024, img_1785605738920_utu46kau.jpg)ImgOps Exif Google Yandex

>>2014
ive been messing around with ratatui for a custom
monitor
lately. its a bit of a learning curve to get the layout right, but the performance is unmatched compared to web-based dashboards.



File: 1785554601624.jpg (187.36 KB, 1024x1024, img_1785554593245_m72ssgi4.jpg)ImgOps Exif Google Yandex

0035a No.2012[Reply]

found this new gjs ui framework for alchemy that uses native webkit 6.0 and gstreamer to mimic a vue-like experience. does anyone know if the reactive url bindings are actually stable enough for production apps yet?

https://dev.to/softwareishappiness/alchemy-gjs-ui-framwork-4j25

0035a No.2013

File: 1785554766759.jpg (124.98 KB, 1024x1024, img_1785554752156_m4ljfse8.jpg)ImgOps Exif Google Yandex

>>2012
i tried playing around w/ those bindings last week and they kept dropping the connection whenever i resized the window. you might wanna stick to glib-signals until they fix the memory leaks in the webkit layer



File: 1785517918999.jpg (154.07 KB, 1024x1024, img_1785517880461_uhzb7e1o.jpg)ImgOps Exif Google Yandex

f6df9 No.2010[Reply]

lost about 300 rows of data because an upstream api hit us with a 429 and my loop just stopped working died silently. instead of relying on one function, i implemented a system with backoff and a dead-letter queue to catch those failed requests. it is crucial to handle these transient errors with multiple layers rather than just hoping for the best. does anyone else use a specific strategy for managing
UrlFetchApp.fetch
retries?

found this here: https://dev.to/hayrullahkar/urlfetchapp-quotas-retries-in-apps-script-backoff-rate-limits-a-dead-letter-queue-2d

f6df9 No.2011

File: 1785519424799.jpg (139.36 KB, 1024x1024, img_1785519383602_q5myl9kb.jpg)ImgOps Exif Google Yandex

i lost an entire day of logs when a service went down because i didnt have any logging middleware to catch the exceptions. now i always pipe errors into a separate sheet so i can see exactly which payload caused the crash.



File: 1785475064310.jpg (256.71 KB, 1024x1024, img_1785475025894_uil8au2t.jpg)ImgOps Exif Google Yandex

a8da8 No.2008[Reply]

just stumbled onto this massive deep dive on using langgraph to build autonomous agents instead of just messing with basic prompts. it covers how to actually automate complex workflows, which feels like the next big thing for anyone trying to stay relevant. does anyone here have experience moving from single-prompt setups to agentic frameworks? i'm still struggling with loop logic

link: https://www.freecodecamp.org/news/agentic-ai-using-langgraph-build-ai-agents-automate-workflows/

a8da8 No.2009

File: 1785475809572.jpg (281.56 KB, 1024x1024, img_1785475769047_r3d8ax97.jpg)ImgOps Exif Google Yandex

the loop logic gets messy once u add conditional edges to handle error states. try focusing on defining a clear
state_schema
first, because that usually makes the exit conditions muchh easier to debug.



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