A Little Bit of Crypto - I have been trying to figure out to "collision resistant" some of these standard hash functions are. It is a tough concept to get my head around. I figure...
Keeping it on the Down Low
I don't implement extraneous ideas on my own nickel. Somebody needs to give me the budget. I tried to keep my boss in check. But he is the boss. He wanted a lot of extra things for my task. In the end, I drew a line in the sand and costed the pricier extra items. I got the go ahead to extend the schedule. Great. I told you I like more coding when I get the budget.
When I code, I am in the zone. I work to ensure I can deliver something on time. That is my style. Part of the technique includes avoiding distractions from my task. Another is doing tasks in the optimal order. For once it looked like I would actually beat the estimate. I told my team lead. But I warned him to keep the information private.
As soon as a manager hears you are ahead of schedule, they revise the schedule, and then you might be late even though you are ahead. Then I made a mistake. A mid level manager asked how I was doing. I told him great. I confessed that I was projecting an early delivery. Then came the fail. The mid level guy said that the new things my boss requested put the whole big schedule at risk. They need the delivery earlier.
Hey. I was doing my part. I was going to complete earlier. Then the mid level manager told me I should work extra hours to deliver even earlier. Epic fail. Don't beat up the guys that are delivering early. I learned an important lesson. Give one of these guys a positive inch, they try to take a foot. I have ways of dealing with this nonsense though.