Hands down the best programming book. It has a great section on abstraction through data structures.
monomon
As others said, in-depth design is often skipped, especially if the dev team started very small. Sounds like your intuition is right, though - the lack of design bit them on the ass when they realized they missed a part.
I have also been laughed at when I suggested a UML diagram in the past. However, it is helpful. For more visually oriented people even more so.
I'd suggest to go ahead and do it, unless your boss is adamant that it is a waste of time. When they see the result they might be happy.
It's a pity it doesn't work with the nvidia drivers. I would've switched by now, otherwise.
Any other recommendations for wayland? I've been through i3, awesome, xmonad.
Solid advice. Try something tangentially related to what you do, at a sufficient but comfortable distance. This will help you grow as a developer. Also totally seconding the last line - it must be fun.
The tee
program is also very useful!
Wow, that's really cheap! I should check it out now.
I was on a PIP early on, and i was also in a low place in my life. The managers were thoroughly well-intentioned, though, and i bounced back, eventually becoming the goto for technical questions in our department, after the team grew a year later. It was a nice place to work. Eventually i quit for something i preferred.
My advice is don't sweat it, put in the work, and try to gauge your managers' intent. Chances are, they are really trying to improve your situation.
Convenience and reproducibility