New ask Hacker News story: Ask HN: Am I a bad stupid engineer? I feel like everything I do is so simple
Ask HN: Am I a bad stupid engineer? I feel like everything I do is so simple
2 by moomoo11 | 0 comments on Hacker News.
I work as a backend/platform engineer and I'm considered a "senior" engineer 6 years of exp, and in the past I've done everything from web UI/backend, mobile apps, and data related stuff. I feel like I understand how to build systems at a high level. So, I feel like a total noob when I show my work to other people. I'm trying to focus on some of my ideas and build out a company around something I can manage to build to 80% and start demoing. Here are my doubts: - I don't really understand how CI works. At work our CI process is massive and honestly confusing/complex. In my case, I have just a few simple scripts that manage this. - I keep my code organized by separation of concerns using some things I've learned from clean code, clean architecture, DDD, etc. Almost everything is a single responsibility, small functions that I can test easily in isolation or as part of larger integration tests, and I don't really do anything fancy or n levels of abstraction. - If it works out of the box with std library, I use it. Otherwise for more complex things or things I don't personally understand, I'll use a well supported library if I don't want to spend a whole day re-inventing the wheel. When I look at other people's code I often have a really hard time understanding what is going on. The tests are confusing, and I feel like I am stupid for not understanding what they're doing in the source code. I also find a lot of the "support" projects like CI, infra, etc. are also complex. At work we have entire teams for all of this, like there's a dozen engineers who work on CI related things, like 30 in infra, etc who support all the teams. Maybe that's why it is complex? At work I'm considered pretty good and I get put on greenfield projects which I hammer out foundations that other people then pick up and build on top of. When I look at external projects or work other people do, I often times just get overwhelmed by the complexity in these projects from the libraries they use to how they structure their code or tests.
2 by moomoo11 | 0 comments on Hacker News.
I work as a backend/platform engineer and I'm considered a "senior" engineer 6 years of exp, and in the past I've done everything from web UI/backend, mobile apps, and data related stuff. I feel like I understand how to build systems at a high level. So, I feel like a total noob when I show my work to other people. I'm trying to focus on some of my ideas and build out a company around something I can manage to build to 80% and start demoing. Here are my doubts: - I don't really understand how CI works. At work our CI process is massive and honestly confusing/complex. In my case, I have just a few simple scripts that manage this. - I keep my code organized by separation of concerns using some things I've learned from clean code, clean architecture, DDD, etc. Almost everything is a single responsibility, small functions that I can test easily in isolation or as part of larger integration tests, and I don't really do anything fancy or n levels of abstraction. - If it works out of the box with std library, I use it. Otherwise for more complex things or things I don't personally understand, I'll use a well supported library if I don't want to spend a whole day re-inventing the wheel. When I look at other people's code I often have a really hard time understanding what is going on. The tests are confusing, and I feel like I am stupid for not understanding what they're doing in the source code. I also find a lot of the "support" projects like CI, infra, etc. are also complex. At work we have entire teams for all of this, like there's a dozen engineers who work on CI related things, like 30 in infra, etc who support all the teams. Maybe that's why it is complex? At work I'm considered pretty good and I get put on greenfield projects which I hammer out foundations that other people then pick up and build on top of. When I look at external projects or work other people do, I often times just get overwhelmed by the complexity in these projects from the libraries they use to how they structure their code or tests.
Comments
Post a Comment