Hosting static blogs using something like Github Pages is an extremely popular way to get blogging without the hassle of a full-blown CMS. One of the major downsides of this, however, is that because the content is static, there’s no easy way to provide search functionality.
I took a back seat on the webinar this week and left you in the very capable hands of our developer duo Chris A and Chris B (Bamford) who showed you some of our more advanced features. Now you may think that you need to a developer to use these features, but I’m here to tell you (as a non-dev myself) that actually the concepts are pretty simple. With just a little bit of extra knowledge you can make our tool do some pretty crazy things. And if you get stuck you can always shoot me an email at email@example.com and I’ll help you figure it out!
Ok, enough of that… Let’s get this show on the road!
DevNetwork releases infographic naming import.io as one of the leading companies in the developer technology landscape
We are thrilled that our technology was recognized in DevNetwork’s Leadership Map of Developer Technology infographic, as a leader in API Services! DevNetwork, producers of APIWorld,DataWeek, and DeveloperWeek, have organized over 120 companies into 9 core groups of technologies across 34 categories in this version one edition of the developer technology industry. The infographic aims at making developer technology understandable to the entire business / technology community.
This morning I read a very interesting article by Jeff Knupp entitled “How DevOps is Killing the Developer”. In it, Jeff argues that developers are at the top of the technical expertise chain (having the most niche, specific expertise), and as such shouldn’t be distracted spending time doing “DevOps” (or indeed QA, sysadmin, database admin, and so on), which he claims require less specific expertise.
On Tuesday, our Developer Experience Engineer, Chris Alexander, took an in-depth look at services available on the AWS cloud, so I made sure to tag along to watch the big show. The event was hosted at Skills Matter alongside the meetup group LJC: London Java Community. The audience of around 100 people were treated to an evening of: Details of using AWS to scale, and tips and tricks based around infrastructure and platform as a service. #LoveLearning.
The concept of breaking companies and teams into smaller groups in order to progress with units of work relatively independently is by no means a new concept. Even with its recent growth in popularity as a way of scaling teams, Amazon have done it for years, and 3M have been at it for decades.
Nowadays, flat-hierarchy organisation structures are all the rage, especially in the Valley. The concept is appealing for a number of reasons: the right people on the right jobs, the promise of easy scaling of the business as it grows, and work happening closer to the customer to name but a few.
As soon as you begin working on a software project that exceeds a few lines of code, managing changes rapidly becomes trickier. To counter this, developers use version control systems to track changes to folders and files.
These systems typically work by tracking changes to files as individual “commits” of work, which then allow you to build up a file’s current state by looking at its initial state, then the series of changes (or commits) that have affected it since then.
Keeping Your Server Clocks Synced EC2 servers are started in sync with the VM host’s clock. They are also configured to use the OS’s standard time servers – for Amazon Linux AMIs, these are *.amazon.pool.ntp.org, and for Ubuntu it’s *.ubuntu.pool.ntp.org. This is great if your server is on “classic” EC2…
Last week, Amazon launched the ability to turn on per-request logging in Elastic Load Balancers (ELBs). This is a much sought-after feature that many users have been asking about for some time now, and finally it is here.
However, logging is only half of the battle. Once you have the logs you have to do something with them in order to be able to figure out if there are any problems that need addressing or improvements that can be made.