In light of seeking a better job and being pessimistic, here’s a failure reel, enjoy!
1 - not getting the basics
Went through two days to realize that toxik.io wasn’t working because the domain was parked, and github / cloudflare / namecheap wasn’t at fault. I applied to those companies the same week. (super tired is how that happens)
2 - early on, I sucked at code
Get calls from the previous job about my old code. Wrote it 3 years ago and it’s terrible because the functions don’t guard against bad values. I list that company as the one where I worked as the guy who wrote automated tests, but my code was filthy and buggy as heck.
3 - I also didn’t pay attention in class
Cryptography is listed as a passion of mine, but I didn’t have enough time over that one summer with the MOOC to even correctly write an XOR one-time-pad canceling bit of code when the pad is reused 10 times.
4 - my code never works for long
I have half of my projects on github as private, because they’re broken / works in progress. It’s arbitrary though, as the public ones are broken as well. Really, when I say I know python, that code doesn’t do a decent job of showing it. (or rust for that matter)
5 - I bitched about people
The startup only gets things done when the co-founder (who doesn’t code python/js), is on break, to offload testing / copy/paste. He’s great because of his business connections, but I’ve bitched about him in the past and I regret it. Kinda a good chap to have around.
6 - I don’t end business relationships well
I leave jobs unexpectedly fast when I’m not getting paid enough to afford food. This has happened twice, either the wage or the hours. Walmart night shift sucks, but it’s full time at $11.40.
7 - thoughts aren’t continuous
Articles I’ve started to write for the local paper (which has reporters gracious enough to be friends with me), died when I went to night shift. Plus, I sucked at copy-editing.
8 - conform to good design principals? ha.
The congredi/perdita/peligro/pedantra code is just the same repo rewriten from scratch multiple times to try to do everything I want it to do, instead of obeying the UNIX gods and writing something that does one thing good.
9 - documenting what I was doing? never
I complain about golang’s docs when my code suffers from severe lack of documentation (in edition to the whole “not working” thing…)
10 - I don’t ask for help
Sometimes, I silently let things drown, without asking for help. Everything feels so simple when it works…
I would like to think of myself as a well balanced person who’s learned from their mistakes. I ask for what I need, and set realistic expectations. When I don’t know how to do something, I’m gracious enough to ask.
I can work unattended on the things I’ve trod before (which, at this point, is getting to be a lot), but still feel like I need time to play around ahead of using something new (like figuring out what a company uses from their engineering blog).
Holding things in confidence, and writing things that are accurate and convey a point are valuable to me. There’s little of my accomplishments that are behind a non-disclosure, but much more of other’s failings or ambitions that are betwixt us.
Good design is important to me –but so is sleep– and I always try to refactor code to be durable. Filthy code still liters my history (and even more of the history I’ve deleted)
Remember to write a conclusion…