Good enough for someone to pay me for it. I've learned not to think too hard about it beyond that.
66Ah yes, the perennial question, "am I worthy of applying for senior jobs already?"
44"No, but somehow I got the job and I'm completely out of my depth."
30Are you me? I got a chance for a gig as enterprise architect and most of the time I have no idea what I'm doing.
2
Programming or knowledge about that has such a high ceiling that the own knowlege always looks like nothing. I always tell myself i do alright to turn down my insecrurities.
31Some cartoonist said everyone has ten thousand bad drawings in them, and the only way to get them out is to draw them.
Everyone's supply of bad code is limitless.
The engineering maxim is that to build something right you have to build it twice, but really, you can keep coding the same thing over and over and over, indefinitely, and you'll keep finding ways that past-you was an idiot. You'll discover there's some terribly clever and beautifully clean way to solve a problem that was once a tremendous pain in the ass. You make this look like progress and growth by abandoning things (sorry, "shipping") and using those clever new solutions in new projects.
In other words, we can't worry that our code might be terrible. It is. Everyone's is, to a more trained eye. And if there's some living ur-coder who is above all others, they look back at things they did last week and mutter "well that was dumb."
10
I mean that's exactly me only that my boss and some coworkers who are super nerds keep praising my working-for-only-1-year-now ass so it's a battle between insecurities and people telling me I'm doing good.
23Trust your coworkers. If you sucked, they wouldn't be saying that.
12
I've seen the code scientists and engineers (not programmers) write. It's real bad
16Me: "Yes"
4It’s a big of a problem.
1amogus
1
