Aaron Jensen

16 Followers
16 Following
50 Posts

@exterm

The semantics of this go beyond the use of "components" at Shopify.

Everyone knows that "modular" implies the thing can be taken out and used in a different context. That's basically verbatim from the dictionary definition. You don't need to be a software developer to know that.

And yet for years the word has been thrown around in discussions of Packwerk as if it's some weaker thing. It's not. Things that are not isolated are not modular. Anything less is something totally different.

A Packwerk Retrospective

In September, 2020, our team at Shopify released a Ruby gem named Packwerk, a tool to enforce boundaries and modularize Rails applications. Since its release, Packwerk has taken on a life of its own, inspiring blog posts, conference talks, and even an entire gem ecosystem. Its popularity is an indication that Packwerk clearly filled a void in the Rails community.

Rails at Scale
🌶️ hot take: we could probably replace ~70 Terabyte of Javascript on the web with simple form submits and users wouldn't mind
[1.0.0] · test-bench/test-bench-1.x@c2bc5f2

Contribute to test-bench/test-bench-1.x development by creating an account on GitHub.

GitHub

I was woken up today by a phone call letting me know that due purely to budgeting changes I’ve been let go from my full-time contracting position I just started in January after being laid off in September.

I am a former #Apple #engineer with 15 years of experience making apps for #iOS and #macOS. I also have experience with #Ruby. Available immediately for full time or contract work.

Please boost. #Swift #RubyOnRails

@collinsworth this was one of the main reasons I stopped using it. When I wanted to do even the most basic things ("remove top border from first item in list", "give posts a slightly smaller font size in modals", etc), the only viable option was to add a bunch of super specific styling props to my components.

This is a dealbreaker for me, because it means I'm writing JavaScript to work around limitations in the styling system. CSS is nearly free, JavaScript is hella-not.

One trap I keep running into with JS/Typescript projects is that to solve problems you need to layer on complexity and that is mostly a fact of life. Moving back to the server-rendered world I feel like I'm back to what made Rails feel so good. If something feels like it's too complex it probably is.

I largely agree with this post. I wonder if the reason that "thick client" became popular again is that client-side development teams became a convenient (read: safe) place to accommodate the industry's massive influx of boot camp grads.

https://www.spicyweb.dev/the-great-gaslighting-of-the-js-age/

The Great Gaslighting of the JavaScript Era

The age of frontend JavaScript frameworks eating the web world didn’t happen simply because some well-meaning developers found great DX. It happened because we were fed a line.

The Spicy Web