One of the engineers on my team got “let go” last week and at first, I thought nothing of it. I didn’t really know what he actually did and from what I hear, he didn’t do much, so it’s not like we all have to take on a lot more work to make up for his absence.
Except now, I’m working on a project that has to use some code he wrote and now I’m feeling the pain. I think I might have an easier time just rewriting the whole thing from scratch instead of debugging his stuff all day.
Usually, if I need to code something big, I first think up an algorithm, or an outline, and then I’ll write it in my code in the form of comments. Then I go through and write the actual code that does what the comments say. I like doing it this way because I get side-tracked easily and it helps remind me what I need to code next.
The way this guy seemed to code was that he wrote comments, wrote out what each function is supposed to output, but didn’t actually write any of the code that actually does what the comments say. Beautiful.
well, at least you know why he was fired :/ I hate working on other people’s code when the documentation sucks.
Your chickpeas/cauliflower looks really good! I often eat chickpeas with onion, tomato and garlic, I think I will try adding cauliflower next time
Whoa!! This is way beyond my head, but I thought I’d comment anyway. I have little knowledge about this engineering stuff and you’re probably one of those geniuses. But I do know food, so I’ll move on to another post!