Over the past year I’ve been favoring class methods over PORO (plain old Ruby objects) for business logic and love this approach. So much easier to organize, test, reuse and refactor.
Static websites worked perfectly for decades We built JS frameworks to build web apps and it worked beautifully Then we applied those frameworks to static websites to solve a problem that doesn't exist We're over engineering the web
I’ve retired from software… process. No scrum, dds, tdd, stand ups, devops, sre, micro services, retrospectives, pre and post mortems… Instead, we just build and run software together. We do use an issue tracker and a good readme. Everyone posts an eod update to our group… twitter.com/i/web/status/1…
@stratejake Supposedly the shorter the feedback cycle you can get, the better pic.twitter.com/yE6YZLFcrV
So good. This here is the level of self awareness all technical people should aspire to. It takes introspection like this to actually improve computers, since most people who happily tolerate esoteric tools usually forget how much pain they went through to become proficient.… twitter.com/i/web/status/1… pic.twitter.com/EEM0QH31wI twitter.com/todepond/statu…
The best way to deal with complexity is to avoid it. YAGNI. There's almost always a simpler solution if you give yourself enough time and space to ruminate on the problem. This principle is similar to achieving high performance. Top performance requires doing less.
This is such a powerful fact for managers and leaders to remember. pic.twitter.com/prURkK6V4Z
This is weird but I'm starting to like making web stuff with just HTML/CSS and vanilla JavaScript No packages No webpack No typescript
Web development has lost its way. The world is mired in a swamp of complex tools and patterns created by those who refuse to see how simple the web could be. It’s so bad that we refuse to see a way out. I want to build a web that’s rooted in the fundamentals.
I used to be all-in on UI components everywhere. Good in theory but often doesn't stand up to reality. Now I find myself helping more and more teams undo these inflexible, hard-to-maintain abstractions. With Tailwind so many of them just melt away. Which is easier to change? pic.twitter.com/EYrBz8ZUwm
How code review is done pic.twitter.com/6nnNMRcO33
Accounts are coming soon on roadmap.sh -- here is the sneak peek of the overall architecture for thos interested 🚀 pic.twitter.com/CtccdwudWK
Maybe the best example I’ve seen of overcomplexification, although I do like Kamran I hate this - implying that this level of complexity is necessary for (from what I can see) is a content site with a few pieces of functionality.
You know what, story time: why “micromanagement” is important for large software companies to culturally embrace, why this is *especially* true for platforms, and how my team learned lesson hard over the past 12 months. twitter.com/alex_danco/sta…
From a DM, just in case anyone else needs to hear this. pic.twitter.com/GZl4twl4wP
Has web development gotten too complicated? pic.twitter.com/mCkCfUYlmG
A small but beautiful project by @raunofreiberg: uiplaybook.dev Pattern library of common UI components. With a detailed breakdown of expected functionality, best practices, accessibility concerns, and implementation tips for each. Great example of 💯 design docs pic.twitter.com/mTbPaa8pmp
Web technology secret: you do not have to ever Frameworks: you do not have to Libraries: you do not have to Compile/build process: you do not have to This decade's pre-processed CSS solution: you do not have to Literally CSS, JS and 99.99% of HTML: you do not have to
Me after finally learning git pic.twitter.com/CGroT1e9SE
I'm beginning to think—as crazy as it sounds—that a company that can think about *anything* beyond hierarchal trees of things has a major competitive advantage the tree-ification of everything: plans, messages, goals, etc. is rampant
*Framework* A lot of people rely on the process A process is useful in a "structured" environment, like in a factory. The problem? We operate in a "wicked" environment. It's better to rely on the principles and framework than the process. 👇🏽 Some of my favorites: pic.twitter.com/StLEv04je7
BREAKING: Client Who Doesn't Have Specific Budget In Mind Absolutely Has Budget In Mind After Hearing Agency's Budget In Mind
Standards-based projects are at an advantage with all these new tools. If you use just plain JS, CSS and HTML, the new tools already support you. For newer standards like native CSS Module Scripts, I'm sure they'll get integrated directly into the tools over time w/o plugins. twitter.com/ScriptedAlchem…
Percentage of origins having good Core Web Vitals for @jquery, @reactjs, and @nextjs and from January 2020 to October 2022. datastudio.google.com/s/kq8LYSQE-7o Any hypotheses as to why jQuery’s percentages are increasing? pic.twitter.com/YKxVgefgas
- Looks interesting
the return of hypermedia is another big inflection point for the web happening rn twitter.com/htmx_org/statu…
The frontend community wants to wash its hands of the decade we lost without naming the causes and consequences of the dogma that swept away better, more grounded approaches and replaced them with MBs of JS. That's not a recipe for healing what was broken.
Talking with a friend about Postgres and DB-Engines database trends (db-engines.com/en/ranking_tre…), it strikes me that all of the big relational databases are falling relative to others, with Postgres gaining share at their expense. A few thoughts as to why this makes sense (1/n) pic.twitter.com/Y85p3yl2W4
In web development people so often reach for tooling to address complexity and perf problems. That's usually just adding complexity on top of complexity. Instead, reduce the need for tooling at all.
When I talk about frontend's lost decade, it's because folks don't grok how long the excesses of 2012-2022 JS "thought leadership" will continue polluting the ecosystem. The UX disaster is radiating from an earthquake of hubris to distant shores like a tsunami of derp. twitter.com/i/web/status/1…