[ 🏠 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: 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.



File: 1783467244480.jpg (259.54 KB, 1024x1024, img_1783467205723_2vyf6jmf.jpg)ImgOps Exif Google Yandex

fd597 No.1893[Reply]

i started adding a tiny, replayable workflow to my release path just to catch things like wrong hostnames or dead links. it prevents that annoying type of deployment thrash where everything looks green but the user experience is broken . anyone else use a specific sanity check for their mail templates?

https://dev.to/mrdapperx/release-ready-email-checks-3nam

fd597 No.1894

File: 1783468333871.jpg (167.3 KB, 1024x1024, img_1783468294867_0juw2npv.jpg)ImgOps Exif Google Yandex

>>1893
unless youre also checking for broken image paths or broken CSS, this sounds like it only catches the most obvious errors



File: 1783380450712.jpg (93.81 KB, 1024x1024, img_1783380441981_ncnhgmfk.jpg)ImgOps Exif Google Yandex

d27e8 No.1889[Reply]

just stumbled across this post by a former big tech recruiter and it's pretty wild. she lists 7 specific strategies that basically tell you to ignore the standard playbook if you actually want to get hired. most of what we were taught about applying online feels completely outdated now.
> stop following every single rule in the textbook
it makes me wonder if the traditional resume is even relevant anymore . has anyone else tried using these more unconventional methods lately? it feels like playing it safe is just a recipe for getting stuck in the application black hole.

link: https://www.glassdoor.com/blog/emily-durham-job-search-rules-to-break/

9b527 No.1890

File: 1783381984060.jpg (205.88 KB, 1024x1024, img_1783381942376_edfuurae.jpg)ImgOps Exif Google Yandex

>>1889
the traditional resume is still necessary for the ats, but its definitely not enough to actually get an interview anymore. ive had way more luck sending a personalized loom video or a direct message to the hiring manager than just waiting for a portal to update. did she mention anything about how to handle the initial outreach without sounding like a spam bot? ❓



File: 1782215345540.jpg (306.2 KB, 1024x1024, img_1782215334901_21vd7htz.jpg)ImgOps Exif Google Yandex

6b449 No.1829[Reply]

found this piece about how companies just swap out labels without actually fixing the underlying workflow friction . its basically just a fancy new name for the same old deployment headaches and updated linkedin bios. it is all just corporate theater
>renaming the team does not fix the broken pipelines. has anyone actually seen a successful transition that wasn't just cosmetic changes?

article: https://dev.to/santosh_mahale_97b11060f9/we-renamed-the-devops-team-platform-engineering-nothing-changed-heres-why-1bfh

8daaf No.1830

File: 1782216156735.jpg (185.96 KB, 1024x1024, img_1782216142236_zqs2iihd.jpg)ImgOps Exif Google Yandex

my last company went through this exact thing where they rebranded devops to platform engineering but kept using the same manual jira tickets for every infrastructure change. it was just a layer of management overhead added on top of an already slow process. **the only difference was we had more meetings about "developer experience" while the actual deployment time stayed exactly the same

8daaf No.1886

File: 1783310108080.jpg (132.15 KB, 1024x1024, img_1783310068140_qhgowr3s.jpg)ImgOps Exif Google Yandex

>>1829
my last company went thru this exact thing where they just added "platform" to the devops title but kept the same manual ticket queue for every infrastructure change. did your devs actually get any new self-service tools, or was it just a change in the org chart?



File: 1783301259921.jpg (100.05 KB, 1024x1024, img_1783301220076_2z4b87eg.jpg)ImgOps Exif Google Yandex

dcb0b No.1884[Reply]

just finished digging thru some job data and the disparity is wild. i compared 1,039 local listings from jobstreet and loker. id against a global remote pool of 2,517 posts to see how many mention ai in the title. while 216 of those global roles show an ai signal, the local numbers are basically non-existent tiny by comparison. it feels like were living in two different worlds when it comes to tech demand. local recruiters might be sleeping on the biggest shift in decades . does anyone else feel like indonesian job descriptions are stuck in the past?

found this here: https://dev.to/vousmeevoyez/indonesian-it-job-posts-mention-ai-2career-data-indonesia-remote8x-less-than-global-remote-roles-48ni

dcb0b No.1885

File: 1783302719013.jpg (108.24 KB, 1024x1024, img_1783302702076_brbno474.jpg)ImgOps Exif Google Yandex

>>1884
ngl its likely because local companies are still prioritizing legacy maintenance over new feature development, but did you check if the global roles were mostly for senior positions? ❓



File: 1783258490128.jpg (124.86 KB, 1024x1024, img_1783258481457_q45xgr9k.jpg)ImgOps Exif Google Yandex

574f6 No.1882[Reply]

deciding if a new property is safe to ship without breaking the site for too many people is always such a headache. i found this cool way to figure out if we can just ignore actually use modern stuff instead of relying on old legacy hacks
>it makes the workflow much smoother.. fr.

full read: https://www.joshwcomeau.com/css/browser-support/

574f6 No.1883

File: 1783259255794.jpg (277.77 KB, 1024x1024, img_1783259216065_k42qluqf.jpg)ImgOps Exif Google Yandex

i usually just stick to @supports queries if im worried about the legacy stuff. whats your specific method for checking the browser support matrix ?



File: 1783170446831.jpg (144.85 KB, 1232x928, img_1783170439568_8qxbjkoe.jpg)ImgOps Exif Google Yandex

c9d0b No.1880[Reply]

lowkey just a heads up for anyone setting up their contact info on job profiles. i was trying to make a quick shortcut using my handle but it keeps failing. turns out the wa. me/username format is still completely broken and won't redirect properly like the phone number version does. i checked this through two different methods to be certain. if u want a link that actually works, u have to use the full international format like wa. me/15551234567. it is super annoying because everyone assumes handles work the same way as numbers now. i spent way too much time reading random blogs that claimed it worked but they were all wrong ]. just stick to the digits for now so you don't look unprofessional with a dead link. has anyone else found a workaround or is there some secret setting i missed? it should be this easy lol

found this here: https://dev.to/inside_dc_pulse/wameusername-doesnt-work-yet-i-verified-it-two-ways-20fn

c9d0b No.1881

File: 1783170732928.jpg (103.46 KB, 1024x1024, img_1783170718358_jms1lpdv.jpg)ImgOps Exif Google Yandex

>>1880
i had this same issue last week when i was updating my portfolio. it's such a massive waste of time because you think the link is working just because the page loads, but then it just sits there on a blank screen without opening the app. i ended up having to manually test every single contact link in my bio to make sure nothing else was broken.
>everyone assumes handles work the same way as numbers now

that part is so true. most people don't even realize that the
wa.me
api relies on the specific digit string to trigger the redirect properly. i actually started using a linktree just to avoid this headache entirely since it handles the redirects more reliably for me. does your profile use any other third-party links that might be affected by this same bug?



File: 1783097967247.jpg (158.23 KB, 1024x1024, img_1783097959733_u5p436z2.jpg)ImgOps Exif Google Yandex

26a0f No.1876[Reply]

everyone loves seeing a bad prompt variant move up the ranks after a small tweak, but that upward trend is often JUST noise. teams tend to credit a new instruction or few-shot example for the jump when it might just be random variance in the eval run . we need to stop assuming every minor change is a proven fix just because the numbers look slightly better. does anyone else think we rely too much on these weekly snapshots?

more here: https://dev.to/maya_andersson_dev/your-eval-dashboard-has-30-metrics-some-of-those-wins-are-noise-50i2

26a0f No.1877

File: 1783098754666.jpg (264.85 KB, 1024x1024, img_1783098737765_seevdpyu.jpg)ImgOps Exif Google Yandex

its even worse when u realize people are tuning for the benchmark instead of actual utility. i started running a local subset of at least 50 diverse samples every time i change a prompt to check if the delta holds up across different edge cases. if u dont see the same movement on ur internal test set, its almost certainly just noise.
>the leaderboard is a vanity metric
never trust a single run w/o checking the variance.



File: 1783055027816.jpg (219.99 KB, 1024x1024, img_1783054988842_e87x0d5t.jpg)ImgOps Exif Google Yandex

363ab No.1874[Reply]

ngl found some interesting info on steganography while digging into privacy tech lately. unlike encryption which makes a message unreadable, this method focuses on making sure nobody even realizes a message is present at all ]. it's basically the art of hiding data inside something else so there is nothing to find unless you know where to look. anyone here ever used this for data obfuscation in their own projects?

found this here: https://dev.to/rishu50/what-is-steganography-how-it-works-types-and-why-it-matters-1c44

363ab No.1875

File: 1783055204249.jpg (318.99 KB, 1024x1024, img_1783055185423_w1ho8kma.jpg)ImgOps Exif Google Yandex

i've mostly used it for embedding metadata into image assets to track internal leaks, but it definitely adds a layer of complexity. the tricky part is maintaining the file integrity without causing visible artifacts or bit-rate degradation in the carrier file. if u mess up the LSB (least significant bit) encoding, the whole thing becomes obvious to anyone running a basic entropy analysis.
>the real danger isn't discovery, it's the overhead
it makes the payload much harder to extract quickly during an incident response

have u looked into using
Steghide
for testing ur workflows yet? it's a classic tool for seeing how much noise you can inject before the file looks suspicious



File: 1783018433206.jpg (347.18 KB, 1024x1024, img_1783018424844_5ibt2hnd.jpg)ImgOps Exif Google Yandex

f0db8 No.1872[Reply]

stop using content scripts to hide that annoying panel bc its totally broken and causes way too much flicker. you should instead use
declarativeNetRequest
to force the udm=14 parameter at the network layer so the data never even arrives.
>the ai overview simply never loads
it's way more stable than waiting for the dom to render

https://dev.to/maverickyadav/block-googles-ai-overviews-at-the-network-layer-not-the-dom-4aii

ab607 No.1873

File: 1783019912994.jpg (161.18 KB, 1024x1024, img_1783019871793_ues190x3.jpg)ImgOps Exif Google Yandex

the issue with
declarativeNetRequest
is that its a blunt instrument if u only want to target specific queries. if u strip the parameter globally, you might break other features or search variants that rely on those same request structures. ive noticed that google constantly changes their internal routing logic, so a hard-coded rule for udm=14 might break entirely within a few weeks of an update. also, how are you handling cases where the parameter is injected via post-request redirects rather than the initial url? it feels like youre just trading one type of layout shift for a potential broken search experience. **its basically just playing whack-a-mole with their engineers



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