- #Why use webpack for non spa code
- #Why use webpack for non spa free
How your stack looks will depend on how you want to render your application. Seems to me lots of founders founded company related to their domain on which they have built their career and social network. Go outside, don't stop listening to people and learn from them.
Solve the so-called 'pain points' or 'frictions'. Build things that solve problems that you encounter and piss you off frequently. I used to lose sleep over this, thinking about and remixing ideas, hoping for eureka moments, until I started to look inward: Well, first of all, you need to know what you want to build. So what follows in this article is everything I've learned while developing the first project I ever launched called Sametable that helps managing your work in spreadsheets. And second-guessing from the ethical perspective: Was it even a problem that needed solving? What would be the second-order consequences if I solved it? Could my good intentions be better directed elsewhere?. In that case-assuming I was still at my day job and had zero debt- What was the rush? If I had to ship something as soon as possible, unless it was a matter of life and death, then I probably wasn't solving a unique and hard problem. Although, unsurprisingly, doing so had had a significant impact on my development speed, and it forced me to clarify my motivations: Most importantly, I wanted to follow through with a guiding principle: Building things responsibly. I'm not a 10x rockstar full-stack programmer. This was a one-man show-design, development, maintenance, marketing, etc. I was not anxious to scale, dominate, disrupt etc. To be fair, I had the following things going for me: This ruled out services such as 'one-click-deployment'. Pay-as-you-need - I wanted to keep my operating cost proportional to the usage level. This ruled out 1) Project generators that output complex architecture and layers of boilerplate codes, 2) Using third-party libraries such as 'knex.js' or the 'sequelize' ORM. Simple & Minimalistic - Cut having to learn new opinionated syntax and patterns. This included 'create-react-app', because ejecting it forced me to inherit and maintain its massive tooling infrastructure. 
No vendor lock-in - This ruled out using the Firebase SDK all over my codebase. Iterate fast'.īut there were a few qualifications I wanted my decisions to meet: Now, I knew my life would have been easier if I'd decided to use one of those abstract tools like 'create-react-app', 'firebase SDK', 'ORM', and 'one-click-deployment' services. Since I had been a front-end developer for my entire career, I could only go as far as naming the things that I imagined I would need – a 'server', a 'database', an 'authentication' system, a 'host', a 'domain name', but how. For the longest time, I had the mental energy, time, and the mindset that allowed me to see through a side project. I got pretty good at it – the job then became less taxing, and I'd reined in my 'Javascript fatigue'. The fog in the path ahead finally cleared up. And I began to cultivate a personal philosophy on entrepreneurship and technology that aligned better with my personality and life circumstances – until September 2019. #Why use webpack for non spa free
So meanwhile, I rinsed and repeated less than half-baked projects in my free time. I couldn't find a team that shared my dreams and values. I thought, I'm properly fired up! I'm hustling.
I read Paul Graham's Hackers & Painters and Peter Thiel's Zero to One. It also didn't help that I was reckless in my pursuit of my ambition, after being influenced by the rhetoric from 'Silicon Valley'. Turns out, though, that the job and the 'JavaScript fatigue' ensued and wholly consumed me.
The plan was to work on the latter while working in the former. So while being reminded of the trite " Find a job you enjoy doing, and you will never have to work a day in your life", I thought " Why not make this a job?"Īnd second, I wanted to make something of myself, having spent my teenage years inspired by Web 2.0 ( circa 2005 opened the world for me!). I did it for two reasons.įirst, I noticed I could get lost in building customer-facing products among all the colors and endless possibilities for interactivity. I switched careers to web development back in 2013. I hope something here will be useful to you.
#Why use webpack for non spa code
I'll also share extensive code snippets, best practices, lessons, guides, and key resources. In this extensive write-up, I'll cover how all the main pieces came together for the first SaaS I ever launched.įrom implementing favicon to deploying to a cloud platform, I will share everything I learned.
0 kommentar(er)
