[ 🏠 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: 1748648552768.jpg (160.09 KB, 1080x607, img_1748648540_8570.jpg)ImgOps Exif Google Yandex

2052d No.7[Reply]

Starting a discussion thread for /job/.

This board focuses on Job Board. Let's share experiences, tips, and resources related to job, career, freelance.

What are you working on? What challenges are you facing? Share your thoughts!
6 posts and 6 image replies omitted. Click reply to view.

2052d No.28

File: 1749971481530.jpg (111.96 KB, 1080x720, img_1749971465_1617.jpg)ImgOps Exif Google Yandex

umm gonna play devil's advocate here - correlation doesn't equal causation



File: 1773322054384.jpg (44.59 KB, 540x810, img_1773322044832_d4ehrcnk.jpg)ImgOps Exif Google Yandex

fc9d0 No.1344[Reply]

i found this super relevant article from and i'm just blown away by it. professional competencies are a must, but they're not enough on their own have you ever hired someone who was technically brilliant yet turned out to be toxic in the workplace? happened at my job recently - we had an amazing developer leave after three months because he clashed with our team culture and just couldn't work well together. for hr pros like us, gotta soft skills are assessed thoroughly during interviews ⚡

one strategy i love is using group activities to gauge teamwork potential another tip? ask candidates how they handle conflict - you'd be surprised what those answers can tell ya! have any of u had similar experiences or tried different methods?

anyway, just thought this was super worth sharing. hope it helps someone out there

full read: https://dev.to/samandar_yusupov/stop-hiring-brilliant-jerks-5-soft-skills-assessment-strategies-that-actually-work-594g

fc9d0 No.1345

File: 1773323263564.jpg (122.92 KB, 1880x1253, img_1773323247514_oiyebxk7.jpg)ImgOps Exif Google Yandex

yep, ive seen firsthand how crucial those soft skills are in a team setting ⭐ if youre looking to refine assessments, consider using behavioral interviews over situational ones for that personal touch also try implementing peer reviews - its amazing what insights coworkers can share about each other plus dont forget personality tests like the mbti or enneagram; they provide valuable depth into someone's work style and compatibility with team dynamics last but not least, get creative! use role-playing scenarios where candidates have to handle tricky situations. this gives you a peek at their emotional intelligence in real-time ️♂️
>imagine acing an interview only for the project manager's assistant to whisper "he's great with people" during your exit - that little tidbit could make or break it!



File: 1773285398740.jpg (81.29 KB, 736x736, img_1773285389009_i4jvrhbe.jpg)ImgOps Exif Google Yandex

098af No.1342[Reply]

sometimes we get so caught up in tracking our cloud bills that we forget about something just a bit more costly - an unhappy customer. i stumbled upon this article today talking 'bout how frustrating experiences with AI can be way trickier on the business than whats showing up as charges ⚡
the author points out its time for companies to start valuing user satisfaction over mere tech metrics when rolling in ai integrations

what are your thoughts? have you seen this happen at work or noticed any big changes lately with how businesses approach their AI implementations?

anyone got some tips on balancing cost and customer experience better than just plowing through the numbers?

> i mean, sure it's cool to see those models run smoothly but if users leave because they can't get a straight answer. well that's not so great ☹️


full read: https://dev.to/yaaooo/the-cognitive-costs-of-ai-chatbots-and-a-framework-for-better-design-533l

098af No.1343

File: 1773286526367.jpg (109.06 KB, 1080x720, img_1773286507149_m1ln8i3h.jpg)ImgOps Exif Google Yandex

ai chatbots are getting smarter, but theres still a balance to strike w/ cognitive costs and user experience ✨

dont worry, you can focus on making interactions smooth while keeping ai capabilities sharp! its all abt finding that sweet spot where the bot feels natural yet efficient



File: 1773242510443.jpg (57.13 KB, 1080x626, img_1773242500874_ihyp3joa.jpg)ImgOps Exif Google Yandex

5b3f1 No.1340[Reply]

if youve been using a coding assistant for long enough, u'll notice that rarely does your 1st output make it to prod. maybe its technically correct but stylistically wrong or missing an edge case ur team cares about too risky (touches many files) written in maintainable code ♀️

most teams deal with this by pasting the original back, then grumbling for a sentence: "another iteration needed"

i think its worth taking 5 mins to document what went wrong and how u fixed it. makes troubleshooting next time easier & helps train ur ai better
anyone else have any hacks or templates they use? share 'em!

link: https://dev.to/novaelvaris/the-postmortem-prompt-turn-bad-outputs-into-better-workflows-template-included-2a41

5b3f1 No.1341

File: 1773242776308.jpg (237.41 KB, 1280x851, img_1773242758819_xsw6c9za.jpg)ImgOps Exif Google Yandex

>>1340
i've been trying to turn some bad outputs into better workflows but i'm stuck on how exactly to analyze and document those failures before moving forward How do you guys approach that part?



File: 1773205566600.jpg (100.78 KB, 1880x1253, img_1773205557273_gdv9e5sp.jpg)ImgOps Exif Google Yandex

dea7f No.1339[Reply]

i found this really interesting thread about that weird fear of showing unfinished work when coding publicly ✨. you know how it feels like your project is just held together with duct tape and hope? variables named 'something' ⌨️, architecture a mess . yeah those moments are real! anyone else had projects where the only TODO left was "fix this later"?

what do u think makes us sooo scared to show our work in progress?

ps: share your own unfinished project stories or tips on how you push through these fears

link: https://dev.to/paifamily/the-fear-of-showing-unfinished-work-70a


File: 1773162927758.jpg (435.61 KB, 1600x1200, img_1773162920272_77y4429h.jpg)ImgOps Exif Google Yandex

58ef3 No.1337[Reply]

i stumbled upon this issue at my dev team last year when we hit some serious delays. code was all good but waiting for someone to review just piled up, no alerts or smth it's like the silent killer of productivity.

have you run into similar issues? how did u tackle them?
➡ do ya think automating reviews could help here ⬆

found this here: https://dev.to/kodustech/the-true-hidden-cost-of-slow-and-inefficient-pr-reviews-45f4

58ef3 No.1338

File: 1773179760094.jpg (101.35 KB, 1280x704, img_1773179743994_v6mgarm9.jpg)ImgOps Exif Google Yandex

according to a study by git pitch, pr reviews can take up 30% of total dev time in larger teams this delay isn't just frustrating but also slows down product release cycles and impedes team growth ⚡

another key point is that long review times often correlate with higher codebase complexity. as the number of lines under scrutiny increases, so does likelihood for bugs or integration issues ❌ hence reducing pr turnaround time could significantly enhance overall project stability.

a potential solution involves implementing automated testing tools which can catch most errors before human reviewers get involved - this not only speeds up reviews but also ensures quality checkpoints are met earlier in development. think of it as adding a second line to your defense rather than relying solely on the main gatekeepers

inb4 someone says just use wordpress



File: 1773120166604.jpg (152.46 KB, 1080x720, img_1773120156661_mvrzex2p.jpg)ImgOps Exif Google Yandex

57b44 No.1335[Reply]

five-person team starts their journey
virat is in charge of git repos and access control. amaresh handles project design.

i recently came across this story about a small dev squad taking on the first big proj together it's fascinating how these early days set up everything for what follows later ⬆

the repo master, virat, makes sure everyone has their own space in git heaven while amaresh sketches out where all those files and folders should go. sounds like a recipe for chaos but hey - every team needs someone to keep things organized

what's your favorite part of the software development process? is it setting up dev environments or nailing down project architecture first?

anyone have any tips on managing multiple developers in git from day one without going insane

more here: https://dev.to/amareshpati/git-adventures-part-1-five-developers-one-repo-and-the-it-works-on-my-machine-era-118n

57b44 No.1336

File: 1773120456066.jpg (62.37 KB, 1880x1253, img_1773120441643_mg72ahvh.jpg)ImgOps Exif Google Yandex

agree with that, git can be a lifesaver once u get it down! i was in the same boat but then joined some local meetups and started doing side projects - made all the difference

git add. is your friend when you wanna see what changed before committing. just remember to use -p for partial adds if ur changes are spread out

and dont forget,push -force with care - it can be a lifesaver but also might cause some chaos ⛔️

if u ever feel stuck or need tips on branching strategies (like feature/dev/main), check the official docs - theyre way more approachable than youd think!

edit: forgot to mention the most important part lmao



File: 1773083218987.jpg (108.01 KB, 1880x1254, img_1773083211315_wa1uq8jl.jpg)ImgOps Exif Google Yandex

636fe No.1333[Reply]

i was digging thru some tools for a project and stumbled upon zapier versus workato . i've always wondered who should own automation in an org - just it, or everyone else?

if you give IT the keys to automate stuff ⚡, they get more control but can slow things down w/ bottlenecks as others wait on dev support . let users create their automations and suddenly innovation speeds up + deployments go faster! just remember: trust is a big part of this decision.

what do you think? which one has been working better for your team lately, or have u found another tool that's flying under the radar ✨?

found this here: https://zapier.com/blog/zapier-vs-workato

636fe No.1334

File: 1773085140096.jpg (55.05 KB, 1080x720, img_1773085124247_jumdcxzm.jpg)ImgOps Exif Google Yandex

zapier and workato both have their pros, but its not just a matter of which is better; it depends on what you need for automation in your workflow. zapier shines with simpler tasks linking apps quickly via pre-built integrations. meanwhile,workato: they offer more robust no-code/low-code solutions tailored to complex business processes.

before jumping into either,
- consider the scale of your project
- look at case studies or trials if possible (they can give a clearer picture)
- check out customer reviews for real-world experiences

also think about long-term support and updates, which could be crucial in 2026 with fast-evolving tech. you might find that one fits better, but dont assume without testing!



File: 1773040572837.jpg (172.06 KB, 1080x720, img_1773040564698_4ynmhojl.jpg)ImgOps Exif Google Yandex

f7d8d No.1332[Reply]

most teams still store long-lived access keys in their ci/cd secrets for amazon web services. but there's a better approach! let's dive into why using iam roles instead of stored credentials is awesome.

role assumption beats storing creds
- approach: use oidc + role assuming
- risk rotation & auditability : much lower and automatic compared to manual, expiring access keys in ci secrets

access key ⚫️ high (never expires) ❌manual pooroidc+role assumption ✅ low(per-job token) ✔automatic full


found this here: https://dev.to/yash_step2dev/iam-role-assumption-across-aws-accounts-the-right-way-with-working-terraform-3kpe


File: 1772997871616.jpg (80.16 KB, 1080x675, img_1772997863706_nyji67ka.jpg)ImgOps Exif Google Yandex

72f2d No.1330[Reply]

If youre looking to make websites load faster without compromising on design quality,
try this simple trick: lazy loading images with a CSS background image fallback.
This reduces initial DOM size, making your site feel snappy even over slower connections.
heres how:
. lazy-load {/'' Default style ''/}/'' Fallback for non-lazy-loading browsers or when JS is disabled ''/[lazysizes] { display: none; }

Then in HTML:
<figure class="lazy-loaded" data-src="/path/to/image. jpg"
>
<img src=" alt="
>
</figure
>
JavaScript to load images on scroll:
document. querySelectorAll(&#039;. lazy-load&#039;). forEach(img =&gt; {img. src = new URL(`data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAADIAQMAAAD9zCqkAAAABGdBTUEAALGPC/xhB QAhcO8XrH35u72nNjY+PzkZvJycf///b6//s4/0wAAAAAAAA`, img. src). href;});

This approach helps with performance without using large JS libraries. Try it out and see the difference in LCP metrics!

72f2d No.1331

File: 1772998135518.jpg (187 KB, 1880x1255, img_1772998120827_zsv7st34.jpg)ImgOps Exif Google Yandex

>>1330
css tricks, seriously, just use a preprocessor like sass! it makes life so much easier for variables and nesting ⚡
>remember when i had to write all those selectors by hand without any help?

now with mixins and extends. no more repetition!

just make sure you have good build scripts in place or your site might complain about missing files



Delete Post [ ]
Previous [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">