pooberbee

I'm not talking about thousands of years ago, but I guess you're responding to a comment about thousands of years ago. Maybe we don't disagree, but it's all too common for modern-day colonizers to try and dismiss their very recent actions as if it were ancient history.

It would be impractical to undo every theft that has ever occurred, and yet we still condemn theft, work to prevent it, punish thieves for it, and try to undo what thefts we can.

One serving of peanut butter

When I was doing more remoting into servers, having tmux was great. These days it's all local dev, so it's far less important to me. Plus, I had gotten to a place where my tiling WM, tmux, terminal tabs, and vim tabs were all competing for keyboard shortcuts, and it was driving me crazy.

I prefer to use my WM and a lightweight terminal instead of term tabs or tmux. If another window is going to be short-lived, I won't bother, but for longer tasks I'll move to a new workspace, often opening new terminals and file managers, as needed.

Yeah, it's basically a tiling window manager that lets you expand each workspace horizontally and scroll left and right through it. The value for me is that I often want each window in a workspace to be a certain size. For example, my browser is fullscreen, and my password manager is half a screen off to one side. My terminals are usually half a screen, sometimes stacked if they're just for monitoring or something, and my IDE is fullscreen all the way to the right of them.

Every day in standup

This was not a case of "I agree with you, but...", though. "But" is perfectly appropriate here to contrast between the first statement and the second.

If you want to improve your problem solving skills, I'd suggest solving actual problems. Data structures and algorithms can be very satisfying in their own right, but the real value is in taking a real-world problem and translating it into code.

It also depends what you want to do with your knowledge. There are domains that are deeply technical and require a lot of the things you've mentioned, but they also tend to be pretty hard to break into. A lot of software is not so deep. Any software project will have need for good domain modeling, architecture, and maintainability. Again, these are things best learned through practice.

Perlence subrange 6-36 is good too

The trial and error is important, so you might end up buying a bunch anyway

Shit, I never thought that might be why, but we've dealt with a lot of skin irritation, and our kid prefers keeping a dirty diaper over getting changed. My day is ruined.