Always embraced the concern pattern folks like @jorgemanru commonly talk about in blog posts and videos... biggest issue was the presentation in IntelliJ IDEs!
It just bugged me unnecessarily that there was separation between the 'User' concerns directory, and the User file
Works with PHPStorm, RubyMine, WebStorm, and the rest of the family...
Pending review on the InteliJ marketplace, but you can grab the source (and a ZIP to install manually) from here: https://t.co/xLwlrdekuc
@linear Being able to attribute specific issues to initiatives would be π for those less-than-project tasks, that still contribute to the wider goals.
@artman@linear π I've got some on both Github and a private Gitlab instance, would love to take a look.
Biggest friction for me is the change of context. Linear is our product operating system, and it adds friction not having MR context in Linear.
@matthieunapoli@calebporzio recently touched on this in his podcast with a beautiful demonstration of when this is useful and the perfect example of why this likely came to be https://t.co/u7RAMyGsMV
@calebporzio More excited than before to get my hands on this - every small detail has had some serious attention π₯΅
$99 is more than worth it. Ignore those people throwing stones from outside the village.
@AshAllenDesign This is awesome! Don't fall into the trap of comparing yourself to everyone else's highlights reel - you're onto something good here πͺ
πAsh's books are always a great addition to your library. Having had a sneak peek of some of the chapters, I can tell you this one won't disappoint.
Consuming APIs In Laravel is now available to buy! π
It's the ultimate guide for learning how to build robust and powerful API integrations for your Laravel apps!
π Use the following discount code to get 20% off: CAIL20
https://t.co/L3vm8nSuqv
#laravel#php