It showed I could create a proper project which follows best practices like CI ect. It also helped that it was pretty relevant to the type of business and something that they themselves could potentially find useful.
I do freelance coding work in my spare time and try and combine it with some open source stuff too as a way of boosting my web presence. I recently made £500 in a month doing work in my spare time, not a huge amount but add on a full time job, it's nice to have the extra income.
I started working when I was 18 and I believe I was hired because whilst I still had a really good knowledge of my area (I hope), I was still very cheap to hire £18k per year. This was good for the company I joined as it's a small startup.
I believe that the junior developers my company have hired have all been super eager to impress their bosses and learn new things while still having a huge passion and interest in coding. Whilst we have all been given some time to adjust to our project, we all quickly adjusted and were able to give be benefits very early on. I can't speak for senior developers but these are the main advantages of junior developers.
With regards to relative inexperience of junior developers, I myself have only been coding for a few years now but I have a genuine passion for coding and go home and throw myself into it every night so I believe that I pick myself up there, someone else I work with has been coding since he was 10!! Whilst not having a lot of experience in a professional environment before joining my current company, in the last year or so, I have managed to learn a number of important tools for the job like: mastering linux, built a great knowledge of PHP, built a good knowledge of C, built a great knowledge of JavaScript, built a great knowledge of server administration and last but not least, improved my productivity by at least 10% by mastering vim. It doesn't take long for junior devs to learn this stuff so they're useful to companies.
TLDR; Everyone has something to offer even junior developers.
I've never used or seen jinja before but it definitely has a few features that I'm thinking of adding like block so thanks for the link. Thanks for giving mine a chance too!
First off, thank you for the advice, it's really appreciated!
Things that are going to be added over the coming days:
* Composer support
* Less static or hardcoded API
* More configurable options
* A else clause for foreach loops
* HTML encoding which is enforced and must be opted out of per echo for increased security
Maybe a different file extension, we'll see
With regards to how it compares to twig, the aim is to take a lot of functionality that twig offers and build on that. I feel like twig hasn't gone far enough with it's attempts to build a templating engine.
Don't worry I took it as constructive criticism from the start, this is why I posted the project here in the first place so thank you!
It's one of the nicest features that you can add to a simple front end site, like a portfolio for example. Even better if you write it yourself for the above scenario!