mockingloris

At the end of the day, it's about who ships.

As a dev, it continues to dawn on me that we live in a time of unprecedented opportunities. Likened to past historic moments in the human collective history (the gold rush, industrial revolution, the dotcom bubble).

These phases/periods, saw power shifts and wealth redistribution. (History keeps repeating)

The zeitgeist and varied opportunities scattered about in the many forms of posts, videos, rants/applaud, half-made/vide coded this or that-that AI so...

Enter Vibaslopium:

Think a community driven tool that "vibas" can use to share their code, snippets, context.md/spec/schema/other-coined-term. Slopium miners spin up these slop-piles in sandboxes and debug/fix the code.

Users would pay a slopium fee for slop-pile tasks; code review/fixing and slopium miners in the process mine slopium as they complete tasks. Similar to crypto blockchain miners and gas fees ha ha.

(I was laughing while typing)

Such times, such wonderful and nostalgic times.

│

└── Yarn me; Let's discuss

I visited a blog from a HN thread and observed the site's links and title were very well named; links had shorter names and the titles were not too long and managed to express the link's content/context.

This got me thinking about how my own naming conventions have gradually shifted. I collaborate with AI on more of my projects.

(I have my own process for feeding context but, on specific; TODO#N.gemini.md/TODO#N.v0-dev.md/)

(I use sublime text as my daily editor - I use a used Lenovo Thinkpad running Ubuntu 24.04; 16.04, 2 years prior.)

For context, I code primarily in JavaScript. What are other naming conventions/observations you have stumbled on - on the job?

│

Segue: v0.dev is now v0.app; they noted that a good number of users aren't devs and the TLD had to reflect.

│

└── Yarn me; Let's talk