opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs(daily-email): add 2022-11-11

Browse source
This commit is contained in:
Oliver Davies 2022-11-13 01:00:58 +00:00
parent 806b7013c4
commit 5f6611f136
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
website/src/daily-emails/2022-11-11.md Normal file
View file

@ -0,0 +1,28 @@
---
title: >
Creating a small proof-of-concept application in an afternoon
pubDate: 2022-11-11
permalink: >
archive/2022/11/12/creating-small-proof-of-concept-application-afternoon
# tags:
# - a
# - b
---
This morning, I was asked a “Could you build…” question.
It was an idea mentioned a short while ago and involves a simple, interactive form on the front end that sends requests to a public API, filters the results from the response and displays them to the user.
I’d probably want to hide the API request behind a service responsible for interacting with the API and filtering the results - ensuring that the API could be switched with something else later if needed.
This afternoon, I built a small proof-of-concept application with Vue.js and TypeScript.
There’s no API, or service retrieving real-time results. All of the data is hard-coded within the App component, as well as the code that filters, sorts and returns the results.
The results are shown by adding a `<pre>{{ results }}</pre>` to the page, with a `<pre>{{ state.selection }}</pre>` to show the input data.
There isn’t even any styling, with just some basic horizontal rules to split the page - similar to [these screenshots from Taylor Otwell](https://twitter.com/taylorotwell/status/1203356860818087944) of some work-in-progress versions of Vapor and Nova.
A working proof of concept, or a "spike", answers the initial "Can we build..." question. It can be shown to a client or other stakeholders, act as a starting point for discussions and requirements gathering and then be turned into user stories. It also allows the Developers to validate their initial thoughts and experiment with different approaches.
If the spike is successful, the idea can then be moved forward and implemented in a full way, otherwise, it can be stopped with a minimal amount of effort and time.