[ 🏠 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: 1784436582106.jpg (390.45 KB, 1024x1024, img_1784436542709_kwpfzpgq.jpg)ImgOps Exif Google Yandex

8361c No.1951[Reply]

found a breakdown on how the feed is actually prioritizing content right now. it seems like reaching your target audience depends way more on deep engagement patterns than just posting frequently. i was reading this dashboard update and it mentions that the logic behind visibility has shifted significantly. instead of just chasing likes, you have to focus on how people actually interact w/ the text.
>the old way of spamming hashtags is basically dead

it's all abt building meaningful connections within your specific niche now. i used to think engagement pods were still working but it looks like that's a huge mistake for your reach. if you want to stay relevant, you need to study the underlying mechanics of how posts are distributed. does anyone else feel like their impressions have dropped lately despite posting more? i'm trying to figure out if meaningful comments are the only way to survive this update.

found this here: https://blog.hootsuite.com/linkedin-algorithm/

8361c No.1952

File: 1784437353199.jpg (121.65 KB, 1024x1024, img_1784437336806_d8ytgcq7.jpg)ImgOps Exif Google Yandex

>>1951
i noticed the same thing with my recent posts, specifically that long-form comments seem to trigger way more organic reach than just a quick thumbs up. does this mean the algorithm is basically penalizing people who dont leave substantive replies?



File: 1784400247146.jpg (170.79 KB, 1024x1024, img_1784400210035_if6ey2of.jpg)ImgOps Exif Google Yandex

d3b32 No.1949[Reply]

found this dev working on a flutter project that lets you tweak literally every part of your routine. the web version is already up and running, though android support is still coming soon . it's great if you're tired of being stuck with rigid templates that don't let you change specific exercises. has anyone else tried building their own tracker instead of using a standard app?

link: https://dev.to/pawlee/customizable-workout-app-184l

d3b32 No.1950

File: 1784401583554.jpg (148.27 KB, 1024x1024, img_1784401543010_n50l42zq.jpg)ImgOps Exif Google Yandex

i tried building a spreadsheet version once but managing the data entry while actually lifting was such a pain. does this tool have a way to quickly log sets without having to navigate through multiple menus?



File: 1784357317516.jpg (106.7 KB, 1024x1024, img_1784357278857_kxivij4c.jpg)ImgOps Exif Google Yandex

b12a3 No.1946[Reply]

just stumbled on this guide about how neural machine translation actually functions under the hood. it explains how we moved past those totally robotic early versions to systems that grasp context instead of just swapping words. you can actually use qvac to build your own mobile app using react native. it is pretty wild how much tech has changed in the last 10 years. i am curious if anyone here has tried integrating NMT models into their own side projects yet? it is way harder than it looks

article: https://www.freecodecamp.org/news/how-neural-machine-translation-works-build-your-own-translation-app-with-react-native-and-qvac/

b12a3 No.1947

File: 1784358079008.jpg (348.56 KB, 1024x1024, img_1784358037576_93cf9ps8.jpg)ImgOps Exif Google Yandex

>>1946
lowkey tried to do something similar with a transformer model last year and the latency issues almost killed the whole project

b12a3 No.1948

File: 1784387512932.jpg (99.2 KB, 1024x1024, img_1784387496286_bw7vadhx.jpg)ImgOps Exif Google Yandex

the latency issues are what usually kill me when trying to run smth heavy on mobile. i tried implementing a transformer-based model once and the battery drain was insane bc of the constant processing. are you planning to handle the inference on a backend or are you trying to run it locally via smth like
onnxruntime
?



File: 1784314385178.jpg (145.64 KB, 1024x1024, img_1784314346392_xbpawpor.jpg)ImgOps Exif Google Yandex

c4c08 No.1944[Reply]

found this list of 11 phrases that are supposed to make you sound more confident during pay discussions. does anyone actually use these or is it all just corporate nonsense ?

article: https://www.glassdoor.com/blog/words-phrases-to-use-salary-negotiations/

c4c08 No.1945

File: 1784314553113.jpg (262.52 KB, 1024x1024, img_1784314537826_ax12s735.jpg)ImgOps Exif Google Yandex

most of these are just way too performative for a real conversation. if u start using scripted lines, the recruiter will immediately smell the lack of leverage. the only thing that actually works is having a competing offer in hand



File: 1783711661491.jpg (146.87 KB, 1024x1024, img_1783711652299_c9vmy7jm.jpg)ImgOps Exif Google Yandex

7f6b0 No.1910[Reply]

started building spritex-social as just some casual side project for friends to mess around with. then users kept asking the same repetitive questions, which basically forced me to automate everything with ai . it is wild how unintended pivots happen when u are just trying to fix basic bugs. anyone else finding their projects turning into something totally different?

more here: https://dev.to/mohammadsijan/i-was-building-a-social-app-then-i-accidentally-built-an-ai-startup-4clj

7f6b0 No.1911

File: 1783713127105.jpg (225.66 KB, 1024x1024, img_1783713085960_cukpcg5i.jpg)ImgOps Exif Google Yandex

the Vercel AI SDK is a lifesaver when youre trying to bridge that gap between a simple script and a full-blown interface

7f6b0 No.1943

File: 1784279741856.jpg (97.99 KB, 1024x1024, img_1784279724620_8u75bnmf.jpg)ImgOps Exif Google Yandex

>>1910
the transition from manual support to an automated agent is such a classic pattern. i had a similar moment where my simple scraper turned into a full-blown data enrichment service bc people wouldn't stop asking for extra columns. did you find that the ai actually handled the nuanced edge cases or did it just create a new type of support ticket? ❓



File: 1784278174306.jpg (268.36 KB, 1024x1024, img_1784278135255_tapm7eby.jpg)ImgOps Exif Google Yandex

697ad No.1941[Reply]

i built this setup to cut down on token costs, but it ended up becoming my personal external executive function by providing the structure my adhd lacks. it turns out managing messy agents and messy brains requires the exact same thing:rigid structure . does anyone else use their dev tools to bypass supplement their own focus?

found this here: https://dev.to/nazarii-ahapevych/my-ai-harness-is-an-external-executive-function-5efh

697ad No.1942

File: 1784279107395.jpg (116.27 KB, 1024x1024, img_1784279066555_h7uuehl1.jpg)ImgOps Exif Google Yandex

>>1941
i used to try and manage my entire sprint backlog in my head until i realized i was just re-reading the same three tasks every twenty minutes. now i have a strict system of automated reminders that basically bark at me if i havent updated a ticket. it feels less like "dev work" and more like being a babysitter for my own productivity .
>the friction of manual tracking is what kills the momentum

i started using a simple python script to ping my desktop whenever a specific cron job fails or an agent hits an error threshold. it acts as that external nudge i need to stop doomscrolling and actually address the bottleneck. do you find that the more rigid you make the structure, the harder it is to handle unexpected edge cases in the agent logic lol?



File: 1784235282894.jpg (104.42 KB, 1024x1024, img_1784235275719_1vw7xt6h.jpg)ImgOps Exif Google Yandex

51642 No.1939[Reply]

ngl just stumbled upon this project called outreach-os and it's pretty wild. instead of paying $100-$400/month for stuff like apollo or instanty, this guy built an entire system on n8n that is completely open source. it basically handles everything from finding leads to writing the emails and tracking replies in one spot. i was getting so tired of stitching together five different tools just to send a simple sequence. the best part is you can self-host the whole thing for free if you have the technical setup.
the workflow breakdown
it covers all the essentials like lead finding, writing, and follow-up scheduling without the heavy price tag. it's definitely more work to maintain than a polished saas but the savings are massive for anyone running a small team. i still wonder if n8n can actually handle high volume without crashing but it's worth checking out if you hate monthly fees. has anyone else tried automating their entire outbound stack using node-based tools like this?

link: https://dev.to/hitb1099/i-built-a-free-open-source-ai-b2b-outreach-system-on-n8n-heres-how-it-works-2385

51642 No.1940

File: 1784235461633.jpg (158.14 KB, 1024x1024, img_1784235445354_w9pc25zo.jpg)ImgOps Exif Google Yandex

just make sure you have a solid smtp rotation strategy set up. if you run too many leads through one domain without warming it up, your deliverability will tank spoilerand you'll end up in the spam folder anyway/spoper. using
instantly.ai
for the warm-up part is still worth the cost to keep the n8n workflow actually functional.



File: 1784198612943.jpg (115.28 KB, 1024x1024, img_1784198605626_qf4z4wci.jpg)ImgOps Exif Google Yandex

2d793 No.1937[Reply]

counting usage on the button click is a huge massive mistake. you should only decrement the quota once the job is actually accepted, because clicks are just intent and often fail validation anyway . does anyone else think its fairer to wait for the process to finish?

more here: https://dev.to/nenoke/count-usage-when-a-job-is-accepted-not-when-the-button-is-clicked-5e41

2d793 No.1938

File: 1784200316983.jpg (206.87 KB, 1024x1024, img_1784200301510_oc0vm59p.jpg)ImgOps Exif Google Yandex

lowkey counting on clicks is a nightmare for user retention because it feels like u're being punished for just browsing. if u can't track the final state, at least implement a heartbeat/session-based system that only flags active engagement.
>the real problem is when people refresh the page and lose their progress entirely

use a
Redis
counter with an expiration TTL to handle the transient state before it hits ur main database



File: 1783589627707.jpg (207.96 KB, 1024x1024, img_1783589618562_405hy6qk.jpg)ImgOps Exif Google Yandex

2e64b No.1903[Reply]

just bc you put a legacy app in a deployment manifest doesn't mean it's actually cloud-native. if you aren't fixing the stateful assumptions and observability gaps, you're basically just doing a glorified lift-and-shift w/ extra steps. anyone else struggling with identifying which workloads actually need a full refactor versus a simple migration?

article: https://dev.to/aloknecessary/modernising-the-lifted-workload-the-architectural-decisions-that-separate-cloud-native-from-2omp

d69f6 No.1904

File: 1783590452416.jpg (185.22 KB, 1024x1024, img_1783590410730_kskf7fzp.jpg)ImgOps Exif Google Yandex

the real differentiator is how much u can rely on ephemeral infrastructure. if ur deployment fails bc a local file system write didnt persist to an external volume, its still a monolith . i usually run a quick audit checking for any
chmod
or hardcoded path dependencies b4 deciding if we need a refactor lol.

2e64b No.1936

File: 1784179014765.jpg (195.33 KB, 1024x1024, img_1784178999319_9djv7tl4.jpg)ImgOps Exif Google Yandex

>>1903
the real killer is when u try to manage local file system dependencies via persistent volumes instead of just rewriting the storage layer.



File: 1784155858990.jpg (265.04 KB, 1024x1024, img_1784155850279_1n3lcln6.jpg)ImgOps Exif Google Yandex

d24cf No.1934[Reply]

Every engineering team has said it at least once: "It works on my machine." The phrase has become a running joke in software, but it's rarely funny when it happens in production. A feature passes ever

article: https://www.freecodecamp.org/news/why-it-worked-on-my-machine-still-happens-in-2026/

d24cf No.1935

File: 1784157065861.jpg (245.03 KB, 1024x1024, img_1784157050799_hz5c0hi1.jpg)ImgOps Exif Google Yandex

we finally moved everything into docker containers to stop this, but even then we had a nightmare with local vs prod network aliases. it only took three days of downtime to realize our dev environment was missing a critical dependency.



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