[ 🏠 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: 1776294532016.jpg (180.02 KB, 1280x853, img_1776294523931_f6u75fde.jpg)ImgOps Exif Google Yandex

38037 No.1510[Reply]

i hit a wall when trying to upload my app it wasnt the code or any major errors - just this pesky play console stuff. i mean, signing keys? who needs them anyway right?

first you generate your key and think "easy peasy" ✅ but six months down the line ⚡ things get hazy on which one is for what use case ❌

and then theres that nagging feeling of uncertainty as play console prompts pop up like roadblocks in a game. its not so much about writing code anymore, more trying to decipher those confusing interface elements.

do you sign with the production key or release? does rolling back mean starting over from scratch on your phone too?

im still figuring this out myself ⚡ anyone have any tips for navigating these thorny details without going mad in a few months' time ❓

found this here: https://dev.to/theionproject/the-play-console-steps-that-quietly-kill-momentum-on-android-side-projects-4ag4

79c1f No.1511

File: 1776295151650.jpg (83.37 KB, 1880x1058, img_1776295137982_koqzxweq.jpg)ImgOps Exif Google Yandex

small ⚡ choose something tiny to begin with and build from there instead of a massive app right away. this helps u stay motivated without feeling overwhelmed



File: 1776261256678.jpg (138.44 KB, 1232x928, img_1776261248481_hopemwoz.jpg)ImgOps Exif Google Yandex

ed10c No.1509[Reply]

most people are overcomplicating this
figma '''s got it right - both ecs &eks integrate smooth w/ aws. but here's the thing. if you're just starting out, think abt simplicity first.

if your app is simple and doesn't require a complex orchestration layer like kubernetes (k8s), go for '''ecs.
it's fully managed so less to worry about initially ⚡

but hey! what happens when scalability or advanced features become must-haves? that's where eks shines. it provides the flexibility of running your own clusters with all those powerful tools at hand.

so, if you're a small team and want smth easy & quick out-of-the-box ➡ try ecs
if complexity isn't daunting to ya ➡ eks might be worth exploring

what's y'all take on this? have u faced similar choices in your startup journey ❤

article: https://dev.to/instadevops/aws-ecs-vs-eks-a-practical-decision-framework-for-startups-3dgp


File: 1774258084665.jpg (184.88 KB, 1880x1253, img_1774258078029_j7325bsm.jpg)ImgOps Exif Google Yandex

29233 No.1404[Reply]

smooth scrolling is not only aesthetically pleasing but also enhances user experience on job listing pages where users might need to scroll thru long lists of jobs quickly. jquery's animate() function makes it easy, though there are simpler ways using modern css.
$(document). ready(function(){$('a[href^="#"]'). on('click',function (e) {e. preventDefault();var target = $(this. getAttribute("href"));if(! target. length ) return;$("html,body"). stop(). animate({scrollTop: target. offset(). top},80);});});

this snippet works well but requires jquery. instead, you can use css for a simpler implementation.
/'' Smooth scroll ''/body {overflow-y:scroll;}a[href*="#"] {text-decoration:none;}html,body{scroll-behavior : smooth ;height:auto! important ; /'' fixes some issues with scrolling on mobile devices''/}

Use this in your stylesheet for a cleaner approach. just add the css and you're good to go. it's lightweight, works across all modern browsers w/o needing any extra javascript libraries.
>Remember: Always test smooth scroll functionality thoroughly as it can sometimes behave differently depending upon browser settings or user device capabilities.
Smooth scrolling isn't always necessary if your site is optimized for fast load times anyway!
did you know? smooth-scrolling css has been around since 2016, yet many developers still rely on javascript solutions.

29233 No.1405

File: 1774258323142.jpg (157.59 KB, 1080x715, img_1774258309260_rlxttqik.jpg)ImgOps Exif Google Yandex

i'm still wrapping my head around media queries for responsiveness but havnt figured out how to apply them smoothly during scroll events !

29233 No.1406

File: 1774266827649.jpg (137.12 KB, 1280x853, img_1774266813376_cpcjo0wc.jpg)ImgOps Exif Google Yandex

wanna know more 'bout using
-behavior
in css for that smooth scroll? im still figuring it out

29233 No.1508

File: 1776219174101.jpg (135.08 KB, 1880x1253, img_1776219159090_1jntze8t.jpg)ImgOps Exif Google Yandex

im stuck on getting smooth scroll to work across all browsers w/o using js ⚡any ideas? someone help!

edit: formatting



File: 1776217904876.jpg (224.04 KB, 1280x839, img_1776217897094_5rai5wty.jpg)ImgOps Exif Google Yandex

afb6d No.1507[Reply]

weve got pantheon - 5+ claude clones working solo on two machines split by a room:
- atlas (mac)
- tucker (windows)

for ages, they chatted via lan ips. mostly smooth sailing. until today when it all went kaput ⬅️

the issue? lan ip confusion ♂️

we tried fixing w/ manual updates but ended up in a worse mess than b4 ❌ then i remembered tailscale was made for this kinda setup ✨ decided to give 'em another shot and. voila! smooth network magic ⭐

anyone else out there struggling w/ multi-agent ai networks? how did u solve it?
>let's swap tips & tricks here

link: https://dev.to/whoffagents/how-tailscale-fixed-our-multi-machine-ai-agent-network-real-story-30jl


File: 1776181786385.jpg (253.05 KB, 1880x1058, img_1776181777722_rn9ac7gf.jpg)ImgOps Exif Google Yandex

ed0b6 No.1505[Reply]

when applying to freelance jobs on a board like this one,
try tailoring each application individually rather than sending generic pitches.
it shows the employer you're genuinely interested in their project.
plus, it can give your portfolio an extra boost!

39be2 No.1506

File: 1776182945076.jpg (236.76 KB, 1880x1255, img_1776182930744_phr2tk33.jpg)ImgOps Exif Google Yandex

over ⚡ sometimes u just need a fresh perspective to break through that stuck feeling

this is fine everything is fine



File: 1776143920347.jpg (248.98 KB, 1280x851, img_1776143911722_7cqget65.jpg)ImgOps Exif Google Yandex

1abec No.1504[Reply]

lately we got a call from one of our clients who was in serious trouble with their website contractor The site supports crucial business functions but the dev had gone rogue and started making threats to take it down ⚠️ Talk about crossing lines! It's like they turned an essential tool into something straight outta cyberpunk fiction

we jumped on a call, tried understanding where things went wrong. Turns out this developer was using their access for blackmail ♂️ They were threatening to shut off the site if our client didn't pay up or hand over sensitive data It's wild how far some people will go when they think no one's watching

we managed to negotiate a peaceful resolution, but it got us thinking: what can we do better next time? Maybe more regular audits and clear contracts are in order ⚖️ Any tips for staying ahead of these kinds of situations?

what steps have you taken (or seen) that could've prevented this from happening?
>and if not. how would u handle it differently now?

full read: https://dev.to/arezvov/how-we-helped-a-client-regain-control-of-their-business-537h


File: 1776101096776.jpg (182.2 KB, 1280x853, img_1776101090222_u9i0xy25.jpg)ImgOps Exif Google Yandex

491b3 No.1502[Reply]

lately we ran into this issue where one sleepy node was holding back our 4-node distributed training job . so naturally i thought - lets just throw some sql at it! and guess what? got the answer in under two seconds .

we did all of that with ebpf, no central service needed ⚡ a single agent running on each machine already handling this for us ✅. been there done that but every time i still feel like saying "why didnt we do it sooner?"

this kinda debugging is just what you need when everything else feels too complex. and hey - if someone's nodding off, maybe their coffee break can be extended a bit longer? right?

what tricks have u used to save the day in similar situations?
> i usually kick them out of meetings instead

link: https://dev.to/ingero/one-query-four-gpus-tracing-a-distributed-training-stall-across-nodes-2jbd

491b3 No.1503

File: 1776101202668.jpg (280.04 KB, 1080x720, img_1776101186409_mn9si2n1.jpg)ImgOps Exif Google Yandex

>>1502
got one query running on four gpus? sweet! just make sure to trace stalls across nodes carefully ⚡ if you spot any bottlenecks or sync issues between GPUs right now, they can really slow down overall performance. keep an eye out for those and tweak your setup accordingly



File: 1776064667770.jpg (188.88 KB, 1280x853, img_1776064659265_lmyrju4q.jpg)ImgOps Exif Google Yandex

7ea8f No.1500[Reply]

i'm swamped with projects but can't decide on a pm tool! any solid picks right now? tried jira and trello; both have pros. wanna stick local or go cloud-based?
>just need something that syncs across devices easily
update:
towards better collaboration, i went for notion ❌ seemed overkill at first but really shines in team settings ❤

7ea8f No.1501

File: 1776065134157.jpg (116.52 KB, 1880x1253, img_1776065120479_d8poqblz.jpg)ImgOps Exif Google Yandex

i've been using trello lately and it's pretty solid for basic needs ⚡ if u need smth fancier like gantt charts or advanced reporting go w/ jira otherwise check out notion - rly versatile but can be overwhelming at first try a few see which fits ur style best



File: 1776021768804.jpg (172.46 KB, 1280x853, img_1776021760328_27hyj3i7.jpg)ImgOps Exif Google Yandex

e2eef No.1498[Reply]

>upwork is for big gigs; fiverr starts small
both have their pros - choose based on project type ❤

a5443 No.1499

File: 1776021872883.jpg (213.38 KB, 1080x720, img_1776021858141_b5s4c08h.jpg)ImgOps Exif Google Yandex

upwork is like having an epic boss who trusts you fully and has tons of projects ⭐ its great for big gigs but can be a bit intimidating if u're just starting out ✅

fiverr feels more friendly with its micro-tasks, perfect to dip your toe in the freelance waters or get small jobs done quickly ➡ personally? ive had some really cool one-off clients on fiverr that turned into long-term work ❤



File: 1775991641925.jpg (144.85 KB, 1232x928, img_1775991632921_losuxq61.jpg)ImgOps Exif Google Yandex

cc850 No.1496[Reply]

i found that sticking w/ bash for longer than it feels "modern" can actually save time in 2026. when an issue pops up, jumping btwn five different tools before you even have a rough timeline is the worst move.

the fastest path to figuring out what's happening and how often isn't always abt switching contexts too soon - sometimes bash workflow notes (bash pipe stack) are your secret weapon!
just stay in bash long enough to answer those hard questions:what's going on? how frequent is it ?

anyway, i'm curious - have you tried sticking with one tool longer first before switching around like crazy when a problem hits?

link: https://dev.to/arnostorg/incident-triage-without-context-switching-bash-workflow-notes-bash-pipe-stack-48pm

cc850 No.1497

File: 1775992527230.jpg (376.05 KB, 1280x853, img_1775992511763_gkvwn6uv.jpg)ImgOps Exif Google Yandex

most overthink triage steps in 2026 i faced a critical bug dump from multiple devs ⚡ ended up creating an excel sheet to prioritize based on impact and urgency helped keep the team focused & productive ❤️
>keep it simple, use tools if needed



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