82 lines
4.5 KiB
YAML
82 lines
4.5 KiB
YAML
|
uuid:
|
|||
|
|
- value: 0dd5ea9d-9d43-4a2a-92f5-c140738ffedd
|
|||
|
|
langcode:
|
|||
|
|
- value: en
|
|||
|
|
type:
|
|||
|
|
- target_id: daily_email
|
|||
|
|
target_type: node_type
|
|||
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|||
|
|
revision_timestamp:
|
|||
|
|
- value: '2025-05-11T09:00:51+00:00'
|
|||
|
|
revision_uid:
|
|||
|
|
- target_type: user
|
|||
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|||
|
|
revision_log: { }
|
|||
|
|
status:
|
|||
|
|
- value: true
|
|||
|
|
uid:
|
|||
|
|
- target_type: user
|
|||
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|||
|
|
title:
|
|||
|
|
- value: |
|
|||
|
|
Creating a small proof-of-concept application in an afternoon
|
|||
|
|
created:
|
|||
|
|
- value: '2022-11-11T00:00:00+00:00'
|
|||
|
|
changed:
|
|||
|
|
- value: '2025-05-11T09:00:51+00:00'
|
|||
|
|
promote:
|
|||
|
|
- value: false
|
|||
|
|
sticky:
|
|||
|
|
- value: false
|
|||
|
|
default_langcode:
|
|||
|
|
- value: true
|
|||
|
|
revision_translation_affected:
|
|||
|
|
- value: true
|
|||
|
|
path:
|
|||
|
|
- alias: /daily/2022/11/12/creating-small-proof-of-concept-application-afternoon
|
|||
|
|
langcode: en
|
|||
|
|
body:
|
|||
|
|
- value: |
|
|||
|
|
<p>This morning, I was asked a “Could you build…” question.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>This afternoon, I built a small proof-of-concept application with Vue.js and TypeScript.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>The results are shown by adding a <code><pre></pre></code> to the page, with a <code><pre></pre></code> to show the input data.</p>
|
|||
|
|
|
|||
|
|
<p>There isn’t even any styling, with just some basic horizontal rules to split the page - similar to <a href="https://twitter.com/taylorotwell/status/1203356860818087944">these screenshots from Taylor Otwell</a> of some work-in-progress versions of Vapor and Nova.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
|
|||
|
|
format: full_html
|
|||
|
|
processed: |
|
|||
|
|
<p>This morning, I was asked a “Could you build…” question.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>This afternoon, I built a small proof-of-concept application with Vue.js and TypeScript.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>The results are shown by adding a <code><pre></pre></code> to the page, with a <code><pre></pre></code> to show the input data.</p>
|
|||
|
|
|
|||
|
|
<p>There isn’t even any styling, with just some basic horizontal rules to split the page - similar to <a href="https://twitter.com/taylorotwell/status/1203356860818087944">these screenshots from Taylor Otwell</a> of some work-in-progress versions of Vapor and Nova.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
<p>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.</p>
|
|||
|
|
|
|||
|
|
|
|||
|
|
summary: null
|
|||
|
|
field_daily_email_cta: { }
|