devrob

1. Creating a MacOS native personal finance tracking + networth dashboard, inspired by Gnucash but no complex business stuff (e.g., Tax invoices)

2. Creating a vision / journey board that tracks your life milestones and displays them in a personal mandala / spiral :)

3. Trying to build an visual story telling tool that lets me convert my medium to long form essays into visual animated companions for youtube. e.g.,

Press 'ENTER' to Feel_ // A Techno Phenomenology https://www.youtube.com/watch?v=lq5tlsX8uIM

Do you mean more earnings per share for corporations or real utility impacts on social systems (e.g., more new drugs)

When I ask Claude about the AI ROI, it seems to cite that ~95% of AI PoC's are negative ROI but the 5% that do have ROI tend to have decent return -- my guess is mostly back office clean up to reduce expenses and increase revenue/profit.

IIRC Uber claim their 1.5k/mo budget lead to no new value creation.

FWIW, I look at the situation with similar skepticism. One argument you could make was what Marc Andreesen said with the hypothesis that "all the big companies get nuked", so no new valued gets created but the large market cap companies get eaten by thousands of little pirañas. Obviously, so far, that doesn't seem to be the case.

The idea was to just avoid sending email altogether and just simulate the interaction entirely using Claude.

The idea was to create a quine that runs forever on something like Akash network with its own crypto treasury to support and pay it's bills and try to replicate. It would then talk to an LLM for support and actions on what to do to stay alive.

It got pretty out there. Stored some of the ideas here.

https://github.com/aquaflamingo/catfi

I noticed that when trying to work with Claude Code I burned my token allocation really quickly and with parallel agents, no better. But when I looked at the other repos things felt really complex, for me at least.

I call it "contextd" and imagine it kind of like a context daemon you can always query in your repository for implementation plans, specs or code, etc. I always liked that git lived in your repo in the .git file, so I wanted this to work like that too but without 3rd party hosted databases or multi-repo pollution.

It's written in python at the moment, uses some local models and lanceDB but I might have it re-written in rust for speed :)

https://github.com/aquaflamingo/ctxd

Don't beat yourself up too hard though, you can always pickup a DJ controller and start again :)

And too: the scene has radically shifted, so being a promoter is a large part of the work. It's kind of like eSports in a way.

That sounds like it was out of Last Night A DJ Saved My Life [1]!

[1] https://en.wikipedia.org/wiki/Last_Night_a_DJ_Saved_My_Life_...

[1] https://www.instagram.com/p/DDkjBJhP1Sh/?utm_source=ig_web_c... [2] https://www.youtube.com/watch?v=ISoPHerYsn4&t=1181s [3] Think Cerce, Boilerroom

Moreover, as several commenters have pointed out there has been a big growth in festivals and awareness. Lots of people talk to me about "house music" now, whereas before it was a relatively "underground" thing.

Now, I think there's a question about whether the scale of such events have maintained the same cultural ethos as the early rave days, and that, though I'm not old enough to have participated, is likely a categorical no. There's a greater focus on 'documenting' experiences at these events rather than living it. Here's a clip of an rising group called Kienemusik [tik tok link](https://www.tiktok.com/@as.anca/video/7359750430345186593?q=...), where you can see there's more video taping than dancing. I would venture to say, we are so filled with wonder sometimes that we forget that part of experiencing awe is letting go of ego and just experiencing.

Also Concern #3, is there a subscription for things? o.O

def do_the_thing

  return do_not_do_it unless first_conditional || second_conditional

  okay_actually_do_it

Glad that Rubocop is shipping with Rails though!

Lot's of random stuff from tools, to troubleshooting, to how-tos to random essays mostly with a philosophical bent I guess

- Tool: Indexed Book Note Taking https://blog.robertsimoes.org/posts/tool-indexed-book-note-t...

- Notes: How Dropbox scaled 2007 to 2023 https://blog.robertsimoes.org/posts/notes-how-dropbox-scaled...

- Social Network Behaviour and Taxation Strategies https://blog.robertsimoes.org/posts/social-network-behaviour...

- Four wings of a Software engineer: https://blog.robertsimoes.org/posts/four-wings-of-software-e...

- Return on Intelligence: Transhumanism, Stagnation or Bureaucracy? https://blog.robertsimoes.org/perspectives/on-return-on-inte...

Funny enough your observation of

> "There are more accountants now than then."

could be extrapolated from in two ways

The optimistic perspective might suppose technological development gives rise to new marketplace adaptations and creation of new and tangential jobs. For example, Facebook / Social Networks / Search creating new roles like: Influencers, Social Media Managers, Search Engine Optimization, et cetera.

For the pessimist perspective, I think you could suppose the "end state" of all technological progress in human societies is, eventually, an oligopoly of two industries: bureaucracy (legal) and politics (marketing).

Is this to do with your comfort level in understanding their approach?

> need to invest considerable time understanding the codebase you are working on and the problems your changes are solving before I can even begin to properly think about your changesets

Completely fair.

> during We Just Got New Budget So Let's Recruit All The People month.

Lol

> One might then go look at github repositories as well as scheduling longer meet-and-greets for the most interesting people to make the final selection.

I see, so using the activity and portfolio _after_ the fact as a means to gauge additional signal once the baseline has been met

> Moreover, many publishers don't accept direct applications, or only accept them during specific, brief, time periods - by requiring the author to get an agent to agree to represent them, they are effectively outsourcing that initial screening step)

Interesting, thanks for sharing!

That is a great point! Similar to admissions tests to a college I suppose.

> Their activity might be mostly in a natural language you don't understand, and how could you evaluate that fairly?

Good point as well.

> That said if a candidate provides their GitHub or other portfolio then I think you should consider it just like any other part of their resume, not to replace the coding challenges but as part of the chat about past experience.

I think I understand. Would it be fair to say that, you consider the the "score" of the coding exercises as weighted higher than potentially significant contributions and maintenance of open source projects _because_ they are normalized?

A. System design and architecture

B. Problem understanding and solving

C. Team work and communication including navigating and working with stakeholders

D. Building requirements and negotiating tradeoffs

E. Ability to deliver consistently and reliability

F. Inventive and resourceful thinking

(Obviously this is non-exhaustive, but some top of mind considerations)

But at the end the deliverable is a combination of documentation, code and software is it not?

Supposing $COMPANY had an interview structure as follows:

1. Basic technical screen: Confirm candidate can program

2. System design: Evaluate candidate's ability to design systems

3. Algorithmic problem solving: Evaluate abstract problem solving

4. Behaviourial interview: Determine if candidate is good fit

Where would you map the above A-F or any other critical elements which I may have missed to how they manifest in 1-4?

My only counter consideration might be that one's resume which states:

"I built XYZ at $COMPANY and resulted in $Xm in revenue growth" and one could simply show the person the product or area under which professional worked.

Per your point regarding candidate pool to evaluate, would you consider it fair to say that you see the purpose of the live problems and technical projects as a means of normalizing the ground of analysis (i.e. comparing apples to apples versus apples to oranges)?