Shit, it happened again. Well it's been almost another year since my last post, 10 months in fact. I genuinely have no idea how this happens. Every. Damn. Time. I tell myself that I'm going to smash this blog post thing and I throw out a few articles, feel real proud and then forget
Kanuu, and what it duu. I want to share some progress on one of my products. Kanuu [https://kanuu.io/]. What it's doing, what problem it's solving, and some plans for the future. My last post before this hiatus was about Kanuu too, but this is going to be coming at it with renewed vigor
The last two months; Kanuu.io TL;DR I spent the last two months working on a new product called Kanuu. It can be found here; kanuu.io [https://kanuu.io]. It's a product that provides you with a subscription UI so you can focus on building your product and not maintaining billing stuff. -------------------------------------------------------------------------------- Ok
Series: Micro-Simplifications Micro-Simplifications in Laravel: Pest - for a simpler life This article is part of my "Micro-Simplifications" series, you can find other articles here [https://slashequip.com/tag/series-micro-simplifications/] and and introduction about what this series is about here [https://slashequip.com/micro-simplifications-in-laravel-an-introduction/]. Pest [https://pestphp.com/] is a fairly new testing framework, it sits as a layer over the
Quick Thoughts Quick Thoughts: Laravel Magic Revelation Rollercoaster The last few years of my developer career have been a rollercoaster of revelations. It's been quite the experience but these are some of the main phases went through: Cautiously using Laravel magic and retaining some sense of control Young and naive, maybe, but this stage involved avoiding facades like
Series: Micro-Simplifications Micro-Simplifications in Laravel: An Introduction Recently I've been trying to put my finger on this 'thing' I'm aiming for when I'm developing features and products in Laravel. This way of working that I think every engineer tries for but maybe can't quite achieve because until it's defined, at least for me, it isn't obvious. Engineering
Laravel Domain-driven module service providers I touched on service providers in my previous post about taking a "Sorta-kinda Domain-Driven Structure in Laravel" [https://slashequip.com/sorta-kinda-domain-driven-approach-in-laravel/] and I wanted to expand a little further on how I see the best way to use them as well as sharing some code that works as a base
Laravel Sorta-kinda Domain-Driven Structure in Laravel I'm prefacing with this that I don't enjoy strict 'patterns' when building products. I enjoy TDD [https://en.wikipedia.org/wiki/Test-driven_development] but I don't adhere to it all the time, I enjoy aspects of DDD [https://en.wikipedia.org/wiki/Domain-driven_design] but again going all in....well
IRL On keeping it simple. It's no coincidence I decided to write this post just after moving my site to Ghost. It's been around 18 months since I last wrote anything. Every month I say to my self 'I must write a blog post' and then never do, so what more of a trope-y, developer-esque,
IRL My social media hiatus About a year or so ago now I'd noticed a habit-forming; every morning I'd wake up when my alarm went off, the first thing I'd do was check Facebook, then Instagram, then Twitter. Sometimes I'd go back to Facebook to see if anyone had posted anything in the last 10
