Coding – Process Street

All posts in Coding


4 Types of Software Testing and When You Should Use Them

software-testing-types

The way customers see it, your software release cycle looks like this:

  • Take ages developing the software
  • Beta test
  • Add a few features, fix a few bugs
  • Done!

This isn’t real life. Beta testing is only one type of test your software needs to pass to avoid being a catastrophic failure.

If your software is struggling to get into a usable state, it’s probably because you’re overlooking testing.

Testing is important for two main reasons:

  1. Tests will reveal flaws in your software
  2. Tests will reveal flaws in your software development process

Note: Apart from customer-facing and QA tests, tests are code.

So, keep reading to find the types of software testing you need to make mandatory in your development team, as well as an explanation of how to do it.

Continue Reading

What is Quality Control? An Introduction for Software Companies

software-quality-control

If you’ve been reading our content about the importance of processes, you know the kinds of things that happen when standard procedure isn’t followed. Satellites crash, nuclear reactors melt down, and information security disasters ruin huge corporations.

For software companies, failure doesn’t always have such wide implications but it can mean carelessly shipping a product that creates catastrophic problems for your customers and destroys their trust in you. And of course, it’s a pain in the arse for your development team to fix.

In this article, I’m going to go over some famous software disasters where Quality Control dropped the ball, and look over some common quality control methods.

Continue Reading

How to Manage Developers Without Pissing Them Off

How to Manage Developers

This article is a guest post from Dillon Forrest, a front end developer, startup guy and content creator. Follow him on Twitter for more posts.

If you’ve ever wondered how to attract and retain engineering talent, this post is for you.

Engineers are notoriously difficult to find, screen and onboard. Every candidate who receives your job offer has likely received several others too. And once they do accept, it’s only a matter of time before another company tries to poach them.

It’s time to ask yourself if your developers are really happy, or are your company’s development processes driving them away?

Let’s take a deep dive into the world of Daria the Developer, discussing five common workflow problems, and giving you tips on how to manage developers.

Continue Reading

7 Software Development Processes to Engineer Your Success

software development processes - header

Get Ready to Swat Those Bugs and Up Your Development!

Every programmer and developer makes mistakes. That’s not a criticism by any means; only a couple of posts ago an eagle-eyed user spotted a Freudian slip of mine when “baring” something in mind. Not only is it a vital part of improving in your field, but the freedom to take risks and leave errors also allows the best of the best to flex their muscles and get creative.

I mean, just so long as it doesn’t almost cause World War 3.

“The necessity of selecting and following a formal process for software development is to… avoid wastage of time, money, demoralization in developers, etc.” – Harisha K R

That’s where your software development processes come in! Here at Process Street, we’ve helped to show how processes can boost productivity, save money and all-around improve your business. So, after showing how to ace your IT processes, we’re here for another round to give you the run down on software development processes!

Take your pick from any of these ready-to-use checklists to easily execute your debugging, sprint planning, user story grooming and more. The wild world of software development awaits!

Continue Reading

Is Bad Engineer Onboarding Ruining Your Company?

The following post is a guest contribution from Steve Klein the co-founder of StatusPage.io.
Engineer Onboarding

How long does engineer onboarding last at your company? 1 week? 2 weeks? A couple months? Regardless, it’s a process you think about in the short term, right when a new employee starts. Once it’s done, it’s done, and you can go on to thinking about the million other things that are going on in your company. Right?

Wrong.

The effects of employee onboarding last way beyond when a new person starts working and impact your whole company. If your onboarding isn’t effective, in just 1 or 2 generations of hiring you’re dealing with a team that’s shockingly less productive than it could be — and costing you a lot of money.

Continue Reading

Get a free Process Street account
and take control of your workflows today.

No Credit Card Required