The Security Error'd
by in Error'd on 2014-05-16It’s important to put some barriers in before users can reset their passwords. You don’t want just anyone accessing their account, after all. Bruce had to answer his security question:
It’s important to put some barriers in before users can reset their passwords. You don’t want just anyone accessing their account, after all. Bruce had to answer his security question:
There are abuses of the class system, and then there are those beautiful, snowflake- like cases of abuse, those moments where you see the code, you understand the code, and you wish that, somehow, you could throttle the invisible person responsible for that code. Alex found this example:
public class Record_Base
{
public DateTime RecordDateTime
{
get { return _recordDateTime; }
set
{
if (this.GetType().Name == "Record_PartRegister")
_recordDateTime = value;
else
throw new Exception("Cannot call set on RecordDateTime for table " + this.GetType().Name);
}
}
}
After the latest round of managerial Three Card Monte, Chris found himself reporting to Judith, on a newly formed team. That team was short-handed, which meant Judith needed to interview a lot of candidates. She sent Chris a steady stream of resumes, and he gave his feedback: “Bring this person in,” or “Don’t bother with this one.”
With Lisa, Chris knew they’d discovered the perfect candidate. She had the skills they wanted, she interviewed well, aced the technical screen, and was personable and compatible with the team. He gave her the thumbs up and waited for Judith to make the offer.
Sometimes, a developer just needs to take the long way around. Sure, a line of code like DateTime StartTime = DateTime.Now
looks simple and readable, but what happens if you want the StartTime variable to be not exactly now?
Craig’s co-worker figured out a better solution: