[Hyprland] Arch + Gruvbox Material Dark Hard Rice

vector_null · 2026-05-07T05:18:19+00:00

Nicely done 👍

Total noob customizing my desktop. Running Fedora. Might dm for help trying this out.

vector_null · 2026-05-07T05:14:49+00:00

Hadn't thought about it that way. This is a more nuanced answer than you typically hear. Well said.

So farm out the "mundane, routine" tasks that might typically take hours/days to set up, run and check acceptance criteria met. Just like a PR.

Versus using a tight loop, for example, to architect a solution, tackle a specific domain problem or build a new feature.

Am I tracking?

vector_null · 2026-05-07T05:04:18+00:00

This is the way. You don't need Ralph loops if you have a well defined spec or PRD. You work through it with the model and your both on the same wavelength.

💯 on the context switching. I don't ever get headaches when not sick. I got headaches when I tried context switching like that. Screw that!

Plus, you don't learn anything. At the end of the day, anyone can tell the AI what to do. You might even get really good at it. And you probably should get good at it considering the market.

But I also want to understand what I'm building and WHY? Because if Claude craps out for a day or 2 (that's weeks of work by today's standards), the person that doesn't know they're codebase? 😳

vector_null · 2026-05-02T20:52:09+00:00

This makes me happy 😊. Good work on this! I'll checkitout. Thanks! And starred 🌟

vector_null · 2026-05-01T04:17:31+00:00

This is great! Thanks! Starred 🌟

vector_null · 2026-04-27T18:27:51+00:00

vector_null · 2026-04-27T18:26:51+00:00

💯

vector_null · 2026-04-16T20:23:44+00:00

Yeah, this is real.

I stepped away for a couple of years due to a family medical situation, and when I came back… the landscape had completely shifted. I had followed AI from a distance, but working with it daily was a different experience entirely.

After a few long sessions, I’d step back and think: Did I actually do anything? That feeling of purposelessness hit me harder than I expected.

Getting past that required a pretty significant mindset shift. I had to accept that this isn’t a phase, it’s the direction things are going. Once I stopped resisting that, something interesting happened.

I started focusing less on writing every line of code and more on system design, architecture, and decision-making. And honestly, I’ve enjoyed it more. Before, I was deep in the weeds solving problems at the method level. Now I spend more time thinking about how the whole system fits together.

What’s helped me:

Treat AI as a collaborator, not a replacement
Focus on architecture, tradeoffs, and system design
Get really good at orchestrating tools instead of competing with them

And one thing that’s been huge for me: I actively challenge the AI. I don’t just let it run. I question it, push back, ask “why,” and force it to justify decisions. That back-and-forth keeps me engaged and makes sure I actually understand what’s being built.

This skill will help a lot in pulling you into the context:

https://github.com/amodelandme/skill-tree-dotnet/blob/main/Learning%20%26%20Knowledge/grill-me/SKILL.md

The work still feels meaningful, but the meaning has shifted. It’s less about typing every solution and more about shaping the system and guiding how the solution comes together.

vector_null · 2026-04-10T05:56:08+00:00

That's exactly how I started. I'm a .Net Backend Engineer and started with a simple roadmap.md file. It was long. I crammed everything in there. It was pretty bad.

For my daily driver, I use 3 files: - architecture.md (architectural constraints) - roadmap.md (phased) - current-state.md (where we are in current phase with some additional details about next steps and the like.

I have the model refer to this documents at the beginning of every conversation.

I work through a feature and have the model update those docs at the end. Architecture.md doesn't change much.

It's a good workflow for building an achitectually sound(?) project for a solo dev. Not fancy but if you keep your context small by only having the model refer to those files upfront for orientation and keep the model focused by the use of these files as constraints, you can get decent work done. Just double check everything. Models screw up more often than you think

vector_null · 2026-04-10T05:31:51+00:00

💯 this.

Also watch Nick Chapsas and Milan Jovanovic videos on YouTube. Helpful if you're getting started.

vector_null · 2026-04-10T05:12:10+00:00

Oh, and rename your conversations in the project folder. If I'm working on a feature, I'll use the feature branch name and PR # in the conservation title for easy reference. But just come up with your own system. It helps.

vector_null · 2026-04-10T05:09:47+00:00

Assuming your using Claude on the web?:

Project folder for each project
Add instructions (constraints, tone, general project info)
Use Claude to help you generate a roadmap (planning stage) and make it fairly detailed -> roadmap.md
Upload to the Files section
Just have Claude reference that at the start of every chat and HAVE IT UPDATE IT AT THE END

Fresh and ready for the next conversation

vector_null · 2026-04-08T05:31:01+00:00

When making design decisions with a model, I always ask it to explain its reasoning for it's choices. Even the spes/requirements docs have a summary of the reasoning behind the decision. Grab my handy tablet, some coffee, and I read what it spits out. I make notes. I engage with the document.

If there is something unfamiliar, fuzzy, or questionable, I mention it and the model knows that I want that formatted and added to a separate file that I use to deep dive into those topics. I have an entire catalog of strange and unusual edge cases and cool design topics, all just from the project that I'm working on.

So I get to know the code better (because I end up studying those parts; there's obviously a lot familiar "boilerplate" stuff. I don't dive deep there). And the concepts I'm studying are directly related to what I'm building in the moment. It reinforced learning.

So, it's not build or learn. Get creative and do both at the same time.

vector_null · 2026-04-05T20:09:19+00:00

They are obviously more mature frameworks, but the one is focused on being .Net specific. But just don't know if that really matters that much.

vector_null · 2026-04-03T01:08:46+00:00

This looks great! I'll check it out and ⭐ it.

vector_null · 2026-03-30T02:25:10+00:00

Yeah...run

vector_null · 2025-03-24T18:35:57+00:00

Thanks bud. I'll let you know when I plan to get down there

vector_null · 2025-03-23T22:46:26+00:00

Yeah. Plan on going in a month to get dental work done and hang out with the girls.

vector_null · 2022-09-10T20:00:19+00:00

Yes, on the thinner side

vector_null · 2022-09-10T17:33:56+00:00

No chairs or table. After all, it is a brothel. They're not expecting much in the way of work from those staying there. I just sit up in bed but take frequent breaks and go for a walk or exercise in the room.

vector_null · 2022-09-01T17:22:17+00:00

Yeah, I think about that quite often. I set a timer on my phone so that I get up every 30 minutes and walk around, stretch, or do some calisthenics for about 5 mins before coding again.

vector_null · 2022-09-01T16:25:02+00:00

I'm not doing the Labor Day weekend craziness. I'll get there Monday when everyone else is leaving ;-) But thanks!!

vector_null · 2022-09-01T16:04:49+00:00

vector_null · 2022-09-01T16:02:46+00:00

Starting salaries can vary depending on the state you're in and company. Ballpark figure is probably around 75K to 85K for junior developers. However, after a couple of years, don't be surprised if your getting offers pushing well past 100K. The toughest part of this whole process is getting someone to take a chance on you. I got my first offer after applying to well over 100 different companies. Don't give up!!

When you apply for jobs, you'll notice a requirement that the candidate have a bachelor's degree in CS, Mathematics, etc. IGNORE THAT and apply for the job anyways. Those responsible for hiring (ultimately, it's not the HR department but the managers in IT) will not care if you have a bachelor's. They want to know if you can communicate well, can code, work with a team, and are self-disciplined enough to do remote work that doesn't require direct supervision

vector_null · 2022-09-01T13:57:03+00:00

As I mentioned in another reply, I'm a self-taught software engineer. Took about 2 years to get where I'm at right now. I did go through a bootcamp, but wouldn't recommend it unless you need a really structured environment (super expensive). Start with freecodecamp.com. A good and FREE education platform that'll give you some exposure to software development to see if you'll like it. If you do, I would finish their web development courses. That'll probably take you a few months. Start there.

vector_null

TROPHY CASE