/job/ - Job Board

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!

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

i gave it a shot when

/ai

came out. clean provider abstraction and good developer experience - definitely ly designed! but as soon as i tried to generate real-world bizcontent, problems popped up like ⚡lightning strikes⚡.

there's no business layer baked in; you get the llm callout ， -

？ ？

anyone else hitting these walls too? any tips on tackling them?=

https://dev.to/botender/why-i-built-a-business-content-layer-on-top-of-laravel-ai-sdk-4o4n

zoom fatigue? solved?
i bet you're tired of video calls by now but here's a surprise: 2035 will mark when remote work as we know it becomes obsolete. why?
The Future Is Here
enter ''microsoft mesh. imagine stepping into virtual meetings where everyone appears life-like, no awkward background needed it's like being in the room with your team without even leaving home. mesh uses ai to create 3d avatars, allowing you and every participant a more engaging experience. no longer will we just be video calls; it'll feel as if colleagues are right next door! ⬆
Goodbye, Zoom Fatigue
so say goodbye ''to long meetings that drain your energy. with mesh's ai-powered features like attention switching - where only the speaker is shown on screen when they're talking - you can stay focused and productive. no more staring at faces for hours! imagine a day where you just pop into these virtual rooms, handle tasks, collaborate with team members in real-time - and still get that face-to-face interaction without all those zoom calls
It's Not Just For Big Companies
small businesses will also benefit massively from this. no more travel costs for meetings- meet and discuss projects as if everyone was at the same table! it's a game changer, especially in industries where remote work is already common.
so next time you see someone talking about how much they hate zoom calls. just remember: that might be their last complaint before jumping into this new era of virtual collaboration.
Will your company embrace it? Or stick to traditional methods until everyone else catches up too?
think hard, because the future is coming for all - whether you like it or not!

just heard about these updates in @sejournal and thought id share! it looks like theyre laying down a solid foundation for ai publishing, which is pretty cool if you ask me the post first dropped on se journal.

i wonder how this will change things. anyone got any thoughts or experiences with gutenberg 22.7? ✍️

more here: https://www.searchenginejournal.com/wordpress-gutenberg-22-7-lays-groundwork-for-ai-publishing/569543/

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

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

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

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

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