Following a brief lull, Decentralised Finance (DeFi) is starting to heat up again. For investors that’s great news, although personally I’m far more interested in the technology side of things. (Doesn’t stop me investing on the side, of course!).
A relatively new DeFi project, BSC Station, is turning out to be pretty exciting — both for developers and for crypto investors.
As the name suggests, BSC Station runs on Binance Smart Chain (BSC). In the startup’s own words:
BSC Station aims to build a Full-Stack DEFI with NFT Auction on the Binance Smart Chain. …
CodeBot from Parallel Agile is a full-stack application generator, which can also host your generated application in the cloud. Give CodeBot a domain model and UI wireframes, and it’ll create:
We have more targets, platforms, architectures and languages on the way, but that’s plenty to get started with!
To whet your appetite, here’s a quick CodeBot video that shows a project…
CodeBot from Parallel Agile is a full stack application generator. Give it a domain model and it’ll generate a scalable system in under a minute.
As an added bonus, if you hand it some UI wireframes too, it’ll generate an end-to-end application including a React.js web-app.
As CodeBot is designed to integrate well with agile projects, the idea is that you start with a simple domain model without many details, generate a proof-of-concept, use this to discover new requirements or change existing ones, return to the model and add some details, re-generate, and so on — rinse and repeat, until…
CodeBot from Parallel Agile is a versatile product. Give it a domain model (in the form of a simple UML class diagram), and it will generate a complete, working software stack… from client libraries in a variety of languages, to a secure REST API server working with a choice of back-end databases, and (already available in Early Access) a generated React.js web application.
Software development as an industry regularly embraces change. New programming languages, new software libraries to learn, new versions of software libraries to learn, even entirely new ways of working… as an industry, we face change regularly and as part of our work.
But the novel Coronavirus, and the world’s inevitable and necessary reaction to it, has forced some fundamental changes that are proving to be a stumbling block for a huge number of IT workers.
To understand why, we must first rewind by a fair distance, and see how software development reached the place it is now.
Does the amount of work left always seem to rise during a sprint rather than drop? This happens to a lot of teams, and the cause is almost always the same.
The classic (though often misunderstood and misused) burndown chart represents a running total of the estimated effort remaining in the current sprint. At the start of any sprint it looks optimistic:
Faced with an upcoming programmer interview? It’s pretty much a certainty that you’ll be asked to complete a coding task. This could be a “homework” assignment that you prepare ahead of time, or an on-site programming task done during the interview itself.
Either way, it’s your opportunity to really shine — and I’ll show you how.
Your potential new employer will be looking for qualities such as attention to detail, pace, code cleanliness, fitness of your design, and whether you’ve clearly understood the…
When we develop a new software feature or story, all too often error handling is tacked-on as an afterthought — or worse, when a bug happens to be found. This can result in many edge cases and error conditions simply being missed. Result? A released product with more holes in it than a cheese grater.
But what if there was a way to bake in error handling from the start, and ensure virtually all error conditions have been covered?
In this article I’ll cover three practices that will make your overall testing strategy far more effective.
What’s the difference between a unit test and a component test, and when should you choose which to write? For many developers, an obvious consideration is size — the amount of code a test covers.
By definition, unit tests are “small” as they each cover a single method or class, while component tests are larger as they each cover a group of closely related classes—a component:
What’s up with the following assertion?
Our team must improve its test coverage so that all our code is covered by tests.
Test coverage and code coverage are often used interchangeably, but they mean very different things:
Opinions on which is “better” do vary, but — shocking disclosure alert — I’m a great fan of test coverage and not so keen on code coverage (at least, when used as a stick to hit…