One of the great things about where I work is our commitment to giving juniors a go (for our sister social enterprise, Head Full of Heart, its actually the core mission 👍).
As most of our code repo’s incorporate some kind of node build or run, a question that is commonly asked is how to setup your environment to actually run node.
Well… have no fear 😱, that’s where this short article comes in.
* Just a reminder, this article shows the setup in windows… but setup in Mac or Linux is pretty similar 👍.
Well I’m glad you asked…
Congratulations, you’re reading this article 🎉…. as a heads up, there’s a partner to this article; Setup a webpack built vanilla JS/CSS static site. The partner article has an example of the setup discussed here (both a quick ‘walkthrough’ of the config + example code).
If you’re like me, then embarking on a new side project is often a case of ‘should I use framework special-wings-batman 🦇, or framework flappy-birds-magic 🐥🎩…. ohhh, maybe I should try that new framework, double-unicorns-fantastimal.js 🦄🌈🎉’. …
Congratulations, you’re reading this article 🎉…. as a heads up, there’s a partner to this article; Static sites — how vanilla is still a delicious flavour in its own right. The related article is a bit of an exploration around the why this setup came about. This article runs through a brief overview of setting up a webpack config for a simple static site… but If you can’t be bothered with either the explanation here, or my other article at all (sad emoji 😥), here’s the webpack.config.js required & here’s the github repo of my example site.
Are you a fan of the Default Dark+ theme in vscode? Wish it was just slightly darker? Well have I got news for you! I’ve released a (slightly) darker variant of the Default Dark+ theme that includes a few visual tweaks to minimise the editor chrome, comments & better highlight typings .etc. I’ve unimaginatively called this new theme dark+ REDUX: Even Darker.
skip the niceties if you like; download here.
So what does it look like?
Ever had the problem of finding a neat solution to code split & lazy load components in Angular? I did.. so for a couple of projects I’ve used a framework piece which allows easy lazy loading of a component. Since I’ve found it pretty useful (and I haven’t been able to find an existing similar package), I decided to open source it and release an npm package; ngx-loadable-component.
Something Angular handles super well is the ability to code-split and lazy load routes. This is…
This article is intended for those at a junior developer level 🤓, with a basic knowledge of git, looking to setup a disciplined development workflow. If you’re looking for some starter info on how git works, try checking out this basic run through and muck around with this interactive git cli. I also won’t delve into how to setup the CI/CD part specifically… in that sense its fairly vendor independent, as you could swap out Azure DevOps for another provider if you wanted. Prod me on twitter🐤 if there’s anything you feel is missing — @danharris_io . …
* Wanna skip the niceties? Example code of this pattern is on github here
Recently I was looking into building an API for an internal company system. The API only had to communicate with a front-end, plus be able to fire of a couple of integration processes. The thought crossing my mind was, since we’re in full control of the stack, surely there’s a better way to communicate than to encode all our info into REST URL endpoints then decode them at the recipient end.
I’ve recently been working on an Angular 4 project, using Visual Studio Team Services to manage our sprints, builds and deployments. Compared to other solutions (e.g. Atlassian Suite .etc), I think VSTS brings a bunch of functionality to the table.
As mentioned, we’re able to manage our sprints, git repos, test plans, tests, continuous integration & deployment all through the one service. This is pretty nifty, and works great. Before I sound even more like a covert advertisement for VSTS, it has its downsides; unless you’re operating directly in the land of something like .NET, information on setup for CI/CD…
So you’ve heard the buzz, the lowdown, the word on the street. React is the bee’s knees of frontend development. Being the enthusiastic go-getter you are, you’ve investigated React and now look to giving it a shot in a personal project, beyond simply following a tutorial. Sound familiar? Well this is the path I recently followed in creating my personal portfolio site (danharris.io).
I’d experimented with creating various simple React Apps and decided it was time I finally put together a serious project. Why not create a portfolio site to showcase all this awesome knowledge i’d gained? Great idea huh……
full-stack dev, grad advocate, beer enthusiast, organiser heapsgood dev beers, co-organiser frontend dev ADL