RE: https://mastodon.social/@impactology/116262353769862527

Folks on the TL, for how many of you this is doable every week?

- Journal every day what you learnt

- Publish 1 insight/week from your work

- Answer 2 questions/week on any platform you like

- Co-author 1 piece/month with a peer

Form a pod of 3-4 peers, each peer contributes 1 insight, synthesized into 1 framework and you publish together

You know how there are book clubs for reading? I think there should be one for writing, co-author stuff together.

@impactology They have long been in existence. Just poke around publication records. They exist is all sorts of shapes and forms. There are even some to ensure your papers make it past the reviewers ...
@aeryn_thrace Not academic publications, this is for layman. For folks who work in industry.
@impactology
Apart from the co-authoring it's all possible.
I'd think co-authoring only when you're committed to some bigger project.
@apsara Great, glad to hear that.
@impactology why & what’s the outcome?
Doable each week & work 40hrs? No
-Journal daily things uncovered/learnt/done/thinking- since 1997 in private wiki.
-Publish 1 insight/week from your work-not on a schedule, only in context of shared format e.g. conversation post/podcast/presentation/etc.
-Answer 2 questions/week on any platform you like-only with project team members. Life’s too short for uncontrolled AMAs.
-Co-author 1 piece/month with peers-no. Company peers focused on promotable work.

@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 Considering my background, starting at entry level in 30s I'm not even thinking about ATS as I'll be autorejected so I'm mostly thinking of small companies : startups or agencies that don't use one

@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

RightFit — Temporary Site

Temporary site for RightFit, a proof-of-work based hiring platform. We connect top talent with amazing companies. Full platform coming soon.

RightFit
@impactology this is “portfolio samples of past work” approach which is not new especially for Writers, Designers, Artists, Sculptors, etc.

@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.

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

Ofcourse, very true.

@dahukanna

That's the exact lesson author of this article learnt, debugging got harder for him after vibe coding

https://every.to/chain-of-thought/when-your-vibe-coded-app-goes-viral-and-then-goes-down

When Your Vibe Coded App Goes Viral—And Then Goes Down

Lessons learned when vibe code meets high load

@impactology
It’s always about managing future consequences of your present actions-FAFO
‘I hadn’t slept for almost 24 hours & all I could do was nervously munch trail mix as Codex investigated yet another bug buried deep in codebase that I didn’t understand. It felt less like programming & more like being dumbest participant at a math Olympiad. Needless to say, I was reconsidering my life choices.

My current opinion: If you can vibe code it, you can vibe fix it, might not be able to quickly.’

@dahukanna Curating some front end courses that are sold by individual creators that have autonomy to offer a discount, purchasing power parity prices and focused more on UI craft

Came across Josh Comeau's courses https://www.joshwcomeau.com/

Then Josh Puckett's https://www.interfacecraft.dev/

Emil Kowalski's animation course https://animations.dev/

Josh W. Comeau

Friendly tutorials for developers. Focus on React, CSS, Animation, and more!

@impactology related - https://mastodon.social/@timmitra/116199971892714410

“Exposure does not hire and pay bills”

@dahukanna I've seen people get hired from twitter and also get clients because they consistently posted about their work, so maybe it can't pay bills but could get your work in front of people who you will work with directly rather than going via ATS, HR and multiple rounds

@dahukanna >Co-author 1 piece/month with peers-no. Company peers focused on promotable work.

What about writing with folks you follow online?

@impactology yes and I have but you can’t control other people’s lives & schedule-it’s best effort.
i’ve always involved myself in communities of interest and communities of practice. The connections in those communities is also what’s led to collaborative conference presentations, conference workshops, conference panels, community podcasts, etc.
The hierarchical nature of mid to large sized organisations tends to encourage & produce strict adherents.
@dahukanna Oh wow, which community?

@impactology some specific communities events, sharing knowledge and learning:

UXPA 2025: Designing the UX for AI: Not your typical UX Design -
https://uxpa2025.org/sessions/designing-the-ux-for-ai-not-your-typical-ux-design/

Domain driven design - @virtualddd
Visual collaboration tools - https://leanpub.com/visualcollaborationtools

Effective team collaboration and why we need it for modern product experiences (2022)- https://m.youtube.com/watch?v=WNQ3ZLcW4Mw

Moderated and led a few Papers on systems with @RuthMalan

Designing the UX for AI: Not Your Typical UX Design « UXPA International 2025 Conference