As I'll be writing a number of articles about AWS in the future, I figured it would be a good idea to first introduce the basics. This article will therefore introduce the AWS API, and guide you through setting it up for your own use.
When it comes to software development, quality is often a difficult thing to measure. Often you will be able to recognize it when you see it, but defining why something is well done is harder. Luckily there are a number of tools and standards out there that will enable you to put metrics against your code. This article shows an easy way to combine these.
As professional nerds, we love role-playing games. And we love web development. Naturally, we wondered what a character talent tree for a web developer might look like.
This is just a fun thing, but can still be used to discover areas to improve yourself in. And of course, it’s one of those sites that shows how much fun web development can be.
Via The Loop
On the one hand, technical debt refers to the quick and dirty shortcuts we take and the effect they have on future development. On the other hand, technical debt is also about the things that we don’t do, such as not commenting our code, not developing documentation, not doing proper testing, etc.
Technical debt is an interesting subject, and one that every developer should take into account. In most cases as a developer you will want to have the most elegant solution for your problem, preferably using the latest or coolest technology. Depending on the situation though this might not always be the solution your boss or client wants, usually because that solution is more expensive than the quick hack you were forced to also mention. That’s why before you then end up implementing the quick hack it is imperative to make it clear this will only postpone the “saved” time until a later moment. To be fair, often enough that trade-off might be worth it, even if this would lead to more time in the future.
Another case of technical debt that isn’t really touched on in this article is caused by using old technology. When there is an existing codebase that makes it easy to build something new, but makes use of older or even no longer supported tools it’s important to weigh the downsides of that very carefully. Especially when it comes to a project that will have to be supported for a long time.
In the short term using this might bring about a successful result faster, and using something new will undoubtedly lead to new and unexpected bugs as well. However, looking at the longer term, there are a fair number of problems that might crop up. Ranging from the obvious security problems, upgrade trouble, and performance issues, to even the decreased ability of the future developers to understand the use of the code base.
The version of SCUMM that was used for Maniac probably shared 80 percent or more of the commands used in later games such as Full Throttle.
A great in-depth breakdown of one of the best classical tools for making games. I’ve enjoyed playing many of the games running on SCUMM and aside from the technical details, this article also shows the fun the developers must have had while building it. Definitely worth a read.
Now lastly, have you ever wished to be able to step through your code, line by line, watch expressions, and even step into a function call to see why it’s producing the wrong return value?
While I don’t agree with running your development server on your Mac instead of using a Vagrant box, this is still a pretty good introduction into a very important debugging tool. Having Xdebug set up correctly can save you a lot of time and headaches, and is an actual good reason for using an IDE.
Of course, after the debugging you can continue as normal in Sublime Text, TextMate, or Vim.
At best, one can read between the lines of that bill that there was some pressure to be restrictive in connection with software patents
It seems like I might have been celebrating too early with my link yesterday. According to this article there is far too much wriggle room left, so that it’s pretty easy to get software patented after all. Unfortunately, for some strange reason laws are written in a way that you need to be an expert to understand them; and I’m not.
Which means I can’t say for certain if this article is correct, but it seems likely. Now, if only the NSA hadn’t caused Groklaw to shut down it might have been dissected and explained there.
It’s yet another piece of evidence which makes it more likely life came to Earth on a Martian meteorite, rather than starting on this planet.
While I have my doubts this is close to conclusive proof, the idea of life starting elsewhere isn’t exactly new. And to me personally it’s always been a fascinating theory, as it makes it more likely for there to be life on other planets as well.
The patents system doesn’t work for software because it is almost impossible for genuine technology companies to create new software without breaching some of the hundreds of thousands of software patents that exist, often for very obvious work
Smart decision in New Zealand, making the country an even more awesome place!
[T]he techniques described in this section are generic enough and also work for reversing other frozen Python applications.
It seems that lately every week there is some new security measure is broken. While part of the actual research shows that security through obscurity in the end never seems to work, I am not happy to see that they managed to bypass the two-factor authentication. In defence of Dropbox though, their security keeps improving with every version.
Amazon doesn’t even know what some of their limits are
A nice writeup of a presentation about the way Reddit scaled their architecture using AWS. I always like it when the pros, cons and the learned lessons of choices are laid out like this.
Small drones have been helping a growing number of researchers produce three-dimensional models of Peruvian sites instead of the usual flat maps – and in days and weeks instead of months and years.
As a child I always wanted to become an archaeologist, and on that basis alone this kind of thing is just great. Using drones like this shows how useful they can actually be when they are used for a good purpose. And as the prices keep going down it’s a matter of time before we see more and more uses these drones can be applied to.
Of course, we shouldn’t forget about the other side of the coin of Droney.
Developers everywhere - PHP is not the same as it was even two years ago. Stop acting like it.
As someone who has had to deal with applications in Drupal, Magento, and similar frameworks I can only agree with Jarrod’s statements here. While those are indeed a good reason to look at PHP as something horrible, the way PHP has grown is spectacular. In fact, I believe that it the tools in the community have improved so much that it is probably quicker and faster right now to start a new project while pulling in useful tools with Composer than try to fix an existing codebase.
Who wouldn’t want their deployments to go like this?