or subscribe with
Join 14,100+ readers for one email each week.
Digests » 427
Should you trust Google and friends with your data? The Cloud is a security blackhole: your provider can pry into your stuff and data breaches are commonplace. So we launched Cubbit, a zero-knowledge p2p cloud storage platform, where no server stores your files and no one can access them without your permission - not even us. Give it a try, start a 30-day risk-free trial.
this week's favorite
If you’re a graduate interviewing for a software job and wondering what a typical day is like, here’s some notes from what I did last Tuesday. It was a pretty typical day.
There's been a recent resurgence on twitter and the like about how teams should divide up their testing efforts. In particular, Tim Bray argues compellingly in favor of taking automated testing seriously. Anyone familiar with my writing will know that I'm very much in agreement with him.
Wait, what? BAD coding practices? Yes, you’ve read correctly. The internet is full of good advice and tutorials for developers already. You can find some even on this blog. This article will totally be different though – sorry. But wait, I will show you something even better! It’s five cardinal sins you can commit in your code. Those bad programming practices are so evil that every developer will hate your work. Are you ready to possess this secret knowledge? Come along then.
So you're doubtful at the mention of a "best regex trick"? Fine. I'll concede right away that deciding what constitutes the best technique in any field is a curly matter.
I'm a strong believer in the programming truism that most bad features have a good reason to exist. The much hated goto statement can tunnel out of a deeply nested block structure quickly and cleanly, in experienced hands. A certain amount of type looseness lets code be leaner and less awkward. Memory pointers might make you hate life, but they were critically important for all the years that computer hardware was weaker than a Nest thermostat. And so on.