Howβs it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK π¬π§
Education
11 plus years* active enterprise development experience and a Fine art degree π¨
You can't go shopping without knowing what you want to buy in much the same way you can't use packages without knowing the problem. And here's how to choose the library.
I want to write a to-do list.
Do I need a library
If yes, what problem am I solving.
Is this library solving my problem
Is the code style matching my stack, eg is typescript well supported, could you live without support?
Is the library maintained and regularly
Is the library full of security issues flagged by npm
Does the library use as few dependencies as possible to prevent headaches when managing other dependencies.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
You can't go shopping without knowing what you want to buy in much the same way you can't use packages without knowing the problem. And here's how to choose the library.
I want to write a to-do list.
makes sense, thanks!