@dahukanna >why & what’s the outcome?

To create a visible trajectory of learning to synthesize and package (or make side project out of) when applying for next job

@impactology why visible only to future employers?
Those items are outputs(snapshots of your work at a specific time). If the outcome is you can demonstrate ongoing learning, with evidence, I’d use a narrative backed with a timeline of evidence.

In 2026 most employers use Automated Applicant Tracking System (AST) & getting through those is a skill to master that only considers how well you perform jumping through the AST hoops like filling out CV section in assigned character count, etc.

@dahukanna Or applying on platforms that have orgs that value "skill based hiring" and "proof of work"

https://rightfit.so/

They have explicitly mentioned ">don't attach your resume / cv — we don't read them. proof of work only"

I hope this trend catches up

@dahukanna Yeah, its my only window for getting work I think

And freelance work, platforms like contra.com for which I'll need to build content on socials for a different kind audience that I'm used to.

@impactology to stand out, combine+layer your gem knowledge with what you’re learning about UX.

My Designer focus is getting designed software into people’s hands, even if I have to write code myself, which I tend to do for the fit & finish most developers don’t see/ignore/whatever e.g. bezier curve animation motion for a slide over panel in an interface.
It’s effort for a ‘small human effect’ that makes overall experience pleasant to use as it does not unnecessarily trigger peripheral vision.

@dahukanna > to stand out, combine+layer your gem knowledge with what you’re learning about UX.

That's exactly what I have planned

@dahukanna

A narrative spine that I am going for that connects my past and future project ideas and around which I can make content

Respect people’s limits and bend the system to fit those limits.

Have pinned this on my wall and have to prioritize what can be implemented in 6 months.

Also figuring out a vibecoding workflow that doesn't damage my design assets.

@impactology I would not recommend vibe-coding anything if you want to be intimately familiar with what you produce and for it to be sustainable.

Can you imagine a gem cutter vibe-coding the cuts & setting? They have the intimate and encyclopedic knowledge of all possible settings/effect and select the appropriate one according to that pattern calculus. Off-boarding and fully delegating to a machine does not help learning and/or skilling.

@dahukanna Manually designing to practice retaining the design skill and vibe coding to just get it prototyped along with explanation of the code so I can understand what is happening where and how

I do want to understand frontend coding as well but right now I don't have the time to learn it from scratch

@impactology

Invest personally where you choose.

“vibe coding is like quick-set cement with superglue, you can only pour and set once”. If and when you need to make any changes, it’s a complete redo, including removing what is already there.

So it’s appropriate for “closed system” prototypes, not “open system” production software systems.