After a small pause, I resume our exploration of stateless RESTful security by asking THE big question everyone should consider when deciding to go stateless: is it worth it?
Software companies used to have one goal: to develop efficient applications that users liked. When people switched from desktop to SaaS / web applications, companies were forced to focus on security to avoid being hacked. Now they will have a new mission: to ensure the privacy of their users. At any costs.
It's 8 PM on a Saturday and you get a call from your project manager asking if you could quickly modify a project's code and deploy it in production. You don't feel okay about it? You're absolutely right!
After years of developing software by (incorrectly) applying the Scrum methodology, I have come to this conclusion: Scrum is the new death march. Or rather, Scrum does more harm than good when it's mindlessly requested by managers who are merely trying to show how modern and trendy their development teams are.
This week I resigned from my comfortable, well-paid job. Why on earth would a developer close to his 40s quit a very nice position as an architect/developer?
Scrum: this single word triggers heated debates, passionate evangelization and tales of horror stories. But whether you think it works or not, there is this one thing I've seen some Scrum adopters do, which defies the whole purpose of the methodology. And in my opinion, that is one of the factors that might lead to... epic failures!
When a team of developers works on projects, they need to agree on code conventions, standards, best practices... Wait, do they have to? What are the developers giving up on in order to deliver uniformly-formatted code? In this post i defend the idea that code conventions and standards come with a high price, and that there might be a different way of working together.
Microsoft, Facebook, Twitter... These three incredible tech giants alone brought us, year after year, what contributes in defining today's IT landscape. All share one common weak spot though: their defaults on privacy.
It's an accepted trend nowadays: according to many TDD and BDD are useful tools with many advantages, and to others they are not. In this post I will not start that old debate again. I will however expose to you one great, possibly overlooked advantage in having extensive test/behavior/specifications coverage: a better team collaboration.
I mean, hey, everybody seems to be giving advice on how to be a good, a great, an amazing developer, right? Who wants to be that? Follow my advices to become a lousy developer instead and never look back!