Thoughts on Software
Today, I want to go through how you can implement a search page that reacts to changes to the url with sveltekit. Reacting to URL change rather than another event such as a form submit keeps implementation simple as the load event becomes the main driver for the search behaviour.
Apart from writing code, driving architecture and designing/re-designing solutions; one of the most common activity for Software Developers is exploring a myriad of possible solutions to roll out a feature or improve an existing one.
When considering a particular problem being solved for a stakeholder, it’s always important to consider multiple ways of approaching the problem.
Here are the main things that I consider when making a decision as to which approach should be taken.
As Developers, we build API’s regardless if we intentionally designed them or not – it could be some form of abstraction for data persistence, how you invoke talking to another service that you have internally within your organisation etc.
If we were trying to intentionally try to design a good API, first, we should probably understand what makes a good API – or probably a better start, what is an API anyway?
Continuing from the previous part, where we’ve written and tested our parser using Antlr 4 – let’s now generate a C# parser, and hook it up to search an elasticsearch index.