sibit

This is awesome. I don't do any graphics programming and don't really have any Raylib experience (or keep up with the projects developments) but it inspired me to begin learning C this past few months. I started building my own zero dependency software renderer (all it can do is color the background and render a spinning 2d rectangle). I'm really excited to dig into the rlsw source code later today.

For me it's the people.

I've been at my current company for ~4 years. Every January the upper management folks kick off the same project and every year it dies in the planning/discussion phase. Maybe one or two other "big" projects or initiatives will "start," but it's always the same: lots of meetings between the managers without the engineers or designers, lots of hype about the "big project," meetings start to get delayed, roadmaps and plans never materialize, then people stop talking about the project altogether. Sometimes I buy into the hype because I believe in the projects, other times I try to point out issues/risks. Either way the engineering team as a whole is always ignored.

What keeps me motivated is doing what I can for the people who _actually appreciate_ what I do. I work in manufacturing and spend a lot of time talking to the people on the factory floor. There's nothing better than hearing about their struggles and then a few days or weeks later coming back to them with "Hey, I heard you saying you're having an issue with X, so I made Y. Want to try it out and see if it makes things easier?" And then when they stop by my desk to say "Hey sibit Y is awesome!". That makes the job just tolerable enough to not leave.

I don't need a whole paragraph just: Copilot+ Recall.

I really like the standalone lit-html rendering library but never really saw a need for Lit. Honestly, I find it hard to see a need for more than <any client-side rendering lib> + Web Components when I want client-side rendering.

> we have conditioned people to think they need to do side projects outside of working 40 hours a week

> If that isn’t available, it’s time to change jobs.

From what I've seen most people want to keep their cake and they want to eat it too. They're not willing to change jobs. They're also not willing to work on anything outside of work. Then they complain that their careers are stagnating.

Then again I'm biased. I work on stuff out side of work and I change jobs every 2-4 years so I can work with new technology.

> I feel that the real problem is a lot of people don’t care about collecting requirements.

As someone who _really_ enjoyed requirements gathering for many years and now has become one of the "I don't care let's just build it" people I can assure you that some of us crashed out thanks to Scrum Masters™, Project Managers™, Product Owners™, or any of the other big "A" Agile™ cronies.

5am I go for a 2 mile run with my dog

When I get home I start a pot of coffee

Shower

If it's a work from office day I leave for work at 5:45 (~15 minute drive)

1-2 hours of reading HN, twitter, blogs

I grab my sticky note pad and I create a checkbox list of 3-5 things I want to accomplish

I start working through the list

> You didn't explain how the "bootcamp grads" thought process differs from yours.

In my experience, their thought process starts with "I know framework/library X" and ends with "What library/framework solves my specific problem".

In recent years it seems like they've completely outsourced their thought process to tools like ChatGPT. However, it's been a while since I've worked with a recent college graduate so outsourcing ones thought process may be the new normal?

I have worked with a few bootcamp grads who didn't start their thought process this way but that's something they've had to learn on their own.

I have always found articles/discussions of code reviews fascinating. In the 10(ish) years I've been employed as a programmer I've never worked in a department with more than ten people and every time the work is distributed such that each person works as an IC on their own siloed project(s). Receiving anything besides the "LGTM" rubber stamp or nitpick comment seems almost impossible.

A part of me jokes that Micro$oft only invested in OpenAI because it's the only sensible way to browse .NET/Nuget package(s) documentation. The other part knows it's dreadfully true.

I use tools like a persistence layer for my thoughts. I can "think in words" but my brain defaults to "thinking in pictures" mode. When I think about a database schema I automatically visualize the tables and the connections between columns in a way similar to how most of these tools visualize the schema. My usage of these tools is more or less of me replicating what I see in my mind as a "save state" that I can resume in a day, month, or year.

Pretty much any internal tool/TUI/CLI/library I've created. If I had to guess I'd say at most 25% of the company projects I've worked on have launched AND have consistent usage. Working hard on something just for it to wither crushes my soul but internal projects are different. They're all skunk works projects. No tickets. No project/board. No PM pushing back on how many points (read: hours) something should be. I'm solving real problems that directly impact the quality of life for myself and my coworkers. The best part is getting real, genuine, feedback. If something sucks they'll tell you and they won't sugarcoat it.

I don't think you can compare the productivity of someones passion with someone who's writing code they're told to write at a job.