As new advances in software development have allowed developers to increase their velocity and push out new software at ever increasing speeds, one less measured metric is software understandability. Although it probably seems obvious, when building new software the goal should always be to build software that is as simple and easy to understand as possible.
As most developers will agree, writing code is oftentimes, if not always, easier than debugging. As a simple definition, debugging is the process of understanding what is going on in your code. When speaking in terms of Python, it is a relatively simple process. Every developer has their own personal debugging method or tool they swear by. When it comes to Python, most developers use one (or more) of the following: print statements, traditional logging, a pdb debugger, or an IDE debugger.
Hans Ulrich Obrist once said that “everything I do is somehow connected to velocity”. We couldn’t agree more. As is in most companies, there’s always something affecting your team’s velocity, whether that’s a new work from home routine, a change in budget, or a variety of other reasons. So many influences are out of your control- how do you make sure that your devs are working at optimal velocity?
As they say in the sports world, “instinctively knowing when to run forward, when to ease back, and when to let someone else take over...these are the marks of a great team and a great team player”. Here, in the tech world, we couldn’t agree more.
The modern age of web development that includes modularized, encapsulated web components, has brought us a plethora of tools, technologies, frameworks, and libraries of all varieties. With every such tool that is created to simplify our lives as developers in the long run, there's also a catch we sometimes neglect to consider: the cost of maintenance and performance.
A mere few months ago the majority of the world was forced to change drastically, including the move into a ‘fully remote’ mode of office work. As reality was bearing down upon us, tech managers and CEOs everywhere were huddled together trying to figure out how to not only make it work, but work well.
As we all know, with great power comes great responsibility, and it’s not only Spider-Man who feels the pressure from that. However, in the case of developers, we’d like to change that saying (sorry, Uncle Ben!) to say that with great power comes great limitations. Why, you ask? Well, it really comes down to the power that software developers have.
Today, we’re excited to announce Data On-Prem for development teams that operate in data-sensitive environments. This new feature truly lets you have the best of both worlds, by enabling large enterprises to leverage Rookout as a SaaS offering, while also meeting the rigorous governance and control requirements that these companies often face.
Most companies strive to achieve periods of hypergrowth and when they’re in it, their goal is to remain there, riding those waves up as far as they possibly can. ‘Hyper growth’ is a term first coined by Alexander V. Izosimov. The World Economic Forum, taking it a step further, explained it as a company’s “need to have a compound annual growth rate (CAGR) of greater than 40%.”.
A team of developers comprises several roles, with each contributing their own unique addition to the mix. Sometimes, it feels quite similar to every TV show ever about a slightly dysfunctional group of friends, (cough Friends, IT crowd, silicon valley cough), with each developer adding their own particular touch to not only the product, but the company vibe itself.
