Skip to main content

The Invasion of the Developer Commandos™

I. Why Deploy Commandos?

It's hard to find the best people to solve difficult problems. By deploying Developer Commandos™, you can get great software developed without needing to figure out how to find the software developers.

II. What are Developer Commandos?

Unlike an old fashioned developer, a commando works independently. They manage themselves so you won't need to.

III. How Can You Deploy Commandos?

A. Create a Project

Use a project host like GitHub to create a shared workspace online. Commandos will be able to contribute to your software project through this workspace.

B. Obtain Incentives

Use a cryptocurrency exchange like Coinbase to purchase an amount of a cryptocurrency such as Ether. You will be able to use this cryptocurrency to provide an incentive for commandos.

C. Post Opportunities

Use a bounty network such as Gitcoin to post bounties. A bounty describes the software problem you need resolved, and allows you to attach a cryptocurrency incentive for resolving it. Once posting the bounty, you will simply be able to sit back and wait for commandos to contribute solutions for your approval.

Additionally, you might find it useful to install the MetaMask plugin for Google Chrome. MetaMask is one tool to enable you to attach Ether to a Gitcoin bounty.

IV. The Future of Software Development

At Serafino Software™, we feel like shared workspaces, cryptocurrency incentives, and bounty networks, go a long way towards improving the way you can get software developed by deploying developer commandos.

However, we think development can be improved even further. That's why we're introducing a very exciting technology called AppDirective™. AppDirective™ will allow you to put in a simple description of your problem, known as a directive, and get out the software you need to resolve it. If you are interested in more information, please see below.


Popular posts from this blog

Reality Checks to Demystify Buzzwords

As an IT insider, I feel I have something valuable to offer nontechnical people in terms of correcting misinformation. Here are a few simple tests for some popular buzzwords in tech. When evaluating a product or service, if you can honestly answer Yes to the reality check question, the buzzword probably truly applies. If the answer is No, it is probably fake. agile Does it make the developers happy? blockchain Does it cut out the middleman? cloud Does it automatically scale? microservice Does it only do one thing? object oriented Is it mostly made of interfaces? RESTful When requests arrive at a certain address, are they ready to use (without parsing)? unit test Does it prevent the tested code from touching anything outside itself?

The Importance of Direction

Which would you say is more important: getting somewhere faster, pushing something harder, or going the right direction? It should be obvious that no matter how much speed or power you use, that won't do any good if you're going the wrong direction. It could also be pointed out that early in a journey, even a small change in direction makes a big difference in where you end up. Therefore, we should make sure we have our direction correct, as the first priority.

How (Not) to Handle Different Exceptions

Came across this sample from a certain multi-billion-dollar company, purporting to show how to implement exception handling. I slightly changed a few cosmetic details to make it anonymous. try { // ... } catch (GeneralException e) { if (e instanceof SpecificExceptionA){ // ... } else if (e instanceof SpecificExceptionB){ // ... } } This is a true actual story--you can't make this stuff up. Yeah, I thought it was pretty hilarious; so I felt like I had to share it.