Just read the manual
When a technology feels impossible, documentation can be the shortest path out
OK so you code at work. it doesn’t matter if you did formal studies or if you somehow ended up writing code accidentally. the thing is, both professional and accidental programmers need to read the manual once and for all to end your misery.
we all have this relationship with one or more technologies in our work life.
i had this with kubernetes. We used it at one company. i kind of knew docker so i thought the jump would be easy. Oh god, it was hard. a completely different beast. Their icons were similar, but nothing alike in reality. tried to coast it for so long. then one day, frustrated by my incompetence, decided to read the manual.
oh, it was so good. Didn’t get it all immediately, read terms i’ve never seen and read many pages confused. slowly, it all started making more sense. I got to understand the basics, the concepts, the fundamentals.
I wasn’t an expert by any metric. But now i wasn’t struggling in uncharted territory. I knew the terms, I knew the basics, so i knew how to tackle problems with it. The solution was so close to me. It took me about an hour of focused reading.
now im aware this is something you can do. you can also end your misery whenever you want. just read the manual.