Lol 😂😂

IF LIVES DEPEND ON A SYSTEM

1. Code review, collaboration, and knowledge sharing (each hour of code review saves 33 hours of maintenance)

2. TDD (40% — 80% reduction in production bug density)

3. Daily continuous integration (large code merges are a major source of bugs)

4. Minimize developer interruptions (an interrupted task takes twice as long and contains twice as many defects)

5. Linting (catches many typo and undefined variable bugs that static types could catch, as well as a host of stylistic issues that correlate with bug creation, such as accidentally assigning when you meant to compare)

6. Reduce complexity & improve modularity  -- complex code is harder to understand, test, and maintain

-Eric Elliott

{spoilers, i guess...}

In season 1 episode 4 of Mr.Robot, Elliott plans on using a Raspberry Pi to heat up the storage facility in order to destroy the cassette tapes stored there. If he can get the temperature high enough, it would render those tapes useless. I was just wondering, can a hack like this take place in real life?

Finally got to catch up on last week's episode of Mr. Robot...I must say, Elliott got my mind messed up with all those illusions. O.o

hello , guys.

!rant
"The joy of discovery is one of the best things about being a software developer."
~ Eric Elliott