Wasseem Khayrattee (ka-ra-tey)

🔲 Today, is the 29th Feb 2024 - that's right, it's a leap year, this happens every 4 year. Make this day special Mine started in a special way this early 5AM - with people that matters & people doing things with purpose. Grateful to share my early start of the day with amazing people like: @ThisIsSethsBlog and @louisekarch who are great source of inspiration and positive vibes. ▪️▫️ You still got time to do something special, something that matters, to you. 🫶

@Jody2879 @groundworxdev I have to agree with you on this one.

@groundworxdev It's about general trade-offs, not specific examples. Blocks add infrastructure for editor flexibility that many projects don't need. They make debugging harder and introduce more moving parts than simple templates. The complexity benefits the paradigm, not the client.

Seeing WordPress developers dismiss block-based development while defending the old stack as “real development.” You know the stack: ACF, PHP templates, global CSS, global JS, everything hardcoded in the theme. Here’s the thing, that approach was fine when that’s how WordPress was built. But WordPress fundamentally changed. Now it’s structured, modular blocks with self-contained JS and CSS that fall back to your theme settings. It’s actually beautiful. Clean. Maintainable. Scoped instead of global chaos. But a lot of developers built entire businesses on the old approach. They’re fast at it. Profitable from it. Their expertise is valuable because of it. The new paradigm threatens all of that. If they admit modern WordPress is better, they have to admit their stack is outdated. Their expertise needs rebuilding. Their business model needs rethinking. So instead of learning, they undermine it. “Real developers code properly.” “Dragging blocks isn’t development.” Agencies should be reevaluating this. Gutenberg-native development is easier to maintain, easier to edit, faster to build new themes. Better accessibility support built in. Yes, there’s upfront cost to transition, but once the structure is in place, everything moves faster. You stop spending energy sustaining the old stack and start innovating on better experiences for clients and users. Embrace it, don’t fight it. #WordPress #WebDevelopment #TechThoughts

@dvassallo @Kern_Alan @renatonitta True

@Kern_Alan @renatonitta Why not? Enterprises trust GitHub with all their trade secrets.

I’m liking these OpenClaw patterns from @renatonitta. Using GitHub for the persistence layer is a nice idea. Making the bot prepare and maintain a “recovery kit” to rebuild itself is a clever backup strategy too.

@boykovdesignco @lizengco this

@lizengco Sometimes losing a client is a good thing. It's all a process of failing & learning, as long as you keep moving forward

I lost a client who genuinely loved my work, and it was the best business lesson I ever had. Today, I’ll share the painful pricing lesson that fixed my boundaries forever. When I first started my design studio, I wanted things to feel simple. I hated writing proposals, and I wanted clients to say “yes” fast. So I made everything a flat fee. Website? One price. Landing page? One price. Easy, clean, no back and forth. But I made one rookie mistake. I priced the “thing,” not the variables inside the thing. Because a website is never just a website. It’s page count, messaging, visuals, layout, interaction, animation, and revisions. And those “small adds” pile up fast. This client came from a friend's introduction. He loved our style and was happy with the quality. When he heard “flat fee,” he locked onto it like a promise. In his mind, a flat fee meant unlimited. And that’s where the slow bleed started. It began harmless. “Can we add a few more pages?” “Can we add more images?” “Can we tweak this section again?” Each request sounded small. But each request cost real time. And I kept saying yes. Then I tried to draw a line: this is beyond scope, we’ll need to add hours or add a fee.” The client pushed back immediately: “But you said it was a flat fee, why are you charging more now?” To be honest, I compromised too many times. It felt like I was the only one bending. So I got frustrated, and the collaboration got tense. In the end, he still loved the final website. But he never came back for more work. Losing that long-term client hurt. Not because my work wasn’t good. Because my pricing system wasn’t fair. That was the moment I realized two things: Pricing is not math. Pricing is boundaries. Early entrepreneurship is never perfect. Sometimes you lose money. Sometimes you lose clients. Sometimes you lose sleep. But the lesson is the real profit. That one client forced me to become precise. And today, my contracts are crystal clear because of it. What are some early lessons you have learned building a business?

@AdityaDhingra89 @lazukars

@lazukars Claude Code for sure, but not Opus 4.6 :) People who get that, won’t be amazed.

🚨BREAKING: You can now run Claude Code for FREE. No API costs. No rate limits. 100% local on your machine. Here's how to run Claude Code locally (100% free & fully private):

(Re: Automattic's ecosystem) I always give credit where credit is due. Many of you know I've been frustrated with last year's WP saga. But that frustration didn't prevent me from keeping an open mind. Recently, I've had the privilege of interacting with several people across the Automattic ecosystem. I need to say this honestly: this new wave of people are remarkably empathetic, helpful and genuinely exceptional. My faith is being restored, Sir! I've found myself digging back into their ecosystem with renewed excitement - and for good reason. Automattic has quietly built some impressive tooling and services around WordPress. The kind of infrastructure that makes professional WordPress operations actually... pleasant (well, if you are deep into native WP). I'm also observing very deliberate, strategic hiring. They're not just filling seats, they're onboarding people with deep expertise and strong values. Many I'm already connected with here and I can vouch: these are A-players and good people. I'm even more bullish on @WordPress in 2026 than I've been in years. Not because of hype, but because of the people and the infrastructure being built. The ecosystem is stronger than the controversies. 💡 PEOPLE AT THE HELM > Service/Product cc @photomatt @wordpressdotcom

(Man vs AI - #02) Ironic that Gemini's best practice output advised me to use Claude's best practices.. bro asking me to create a Claude.md file 😜 ## My experimentation so far points to: 💡 CLAUDE > GEMINI > ChatGPT Though the sweet spot lives at the intersection of Gemini and Claude. There are reasoning processes where Gemini genuinely excels. Oh yes, ser! ## Today's breakthrough (?): I cracked prompt idempotence 😜 Well, I managed to create consistent outputs from both Gemini and Claude using a standardized input format. Haven't felt this kind of adrenaline rush since my DEVOPS night owl days. Those "aha moments" hit different when you're deep in the weeds, aye! 🦾 ⚠️ One thing, we, engineers understand better than the average "vibe-coding Joey": idempotence and model-agnostic prompting are non-negotiable for serious AI work. 📈

(Man vs AI?) Productive morning, it seems... 😝 Why didn't AI just give me the fix that actually worked... on the first try? 😤 - 9 attempts - 9 confident explanations - 1 actual solution. This was a trivial bug. I already knew the answer. But I was told to "use AI for everything, everything!". And so I did, ser!👇

We prefer to trust the Terminal.. everything else like your GUI example are just wrappers on top of shell commands. Also for proper devs, a Terminal is the bread and butter in daily routine. It’s like once you learn how to drive a car, you’ll want nobody to drive you around - specially when you have a nice one (yes there are flavors and toppings you can add to your Terminal to make it the most enjoying car around in your yard)

When VS Code already has the Source Control feature, why do developers still use Git commands in the terminal for pushing, committing, or cloning repositories? 👀

@zbrandonz @CodeByNZ Once you get your mind around git, you’ll be like Neo.

@CodeByNZ I honestly had no idea this existed. I hate git. I hate git so much that I've been backing code up to Google drive recently for the sake of simplicity. I'm using this from now on.

@KritikaSaini23 fix

I am a Vibe Coder, scare me with one word.😏

🖖 Shoutout to @strebel

When the marketing Yoda of the OG managed WordPress host AND Former GoDaddy content chief, spends a day moving off AWS + Cloudflare + GoDaddy… I grab popcorn and a notebook. 🍿📝 I’d genuinely love to hear your why behind the move, if you’d be willing to share some of your wisdom, Sir. I might have heard Saint @strebel (my inspiration) speaking of you like legend in the past. 🫡

Spent my day moving our web hosting infrastructure off of AWS, Cloudflare, and GoDaddy. Absolutely wild since my tech career was built off of services from those companies. Hell, for those paying attention over the years, I was the head of content & social at GoDaddy.

@wkhayrattee There's a lot of things most Americans, Australians & Canadians don't understand about Dutch culture. If you have ever studied there or even visited you'll understand a bit about it. It's why DHH is straight to the point, excellent wordsmith & vocabulary. Convention over Config.

(DHH always gives me good vibes) When David Heinemeier Hansson talks, I listen. He has a knack for saying hard truths in the most simple, most direct way and I appreciate that. I think some of us in WordPress (still) need the outside mirror (too). An impartial perspective helps us reflect without the usual baggage. // I quote: // “If you release something as open source, people are free to use it as they see fit. And they are free to donate code or resources or money back to the community as they see fit. You may disagree about whether they’ve done enough or should do more, but you can’t show up after you’ve given the gift of free software to the world and then say, now that you’ve used that gift, you actually owe me a huge slice of your business because you got too successful using the thing I gave you for free. You don’t get to take a gift back. That’s why we have open-source licenses. They stipulate exactly what the obligations are on both sides of the equation.” ~ @dhh // Full interview: // youtube.com/watch?v=vagyIc… // My takeaway: // Open source is a gift with clearly written terms. If we want different outcomes, we should change our licenses or our business models - and not guilt the users and builders who followed the rules. Happy coding! And shout-out to all of you who gift the world with the magic free software that changes the lives of so many of us. 🫶🚀 This gives me even more energy to keep growing in this wonderful WordPress ecosystem. 💚

@wkhayrattee I also kinda started linking this person :D

(Re: Lifetime deals) It still amazes me how forward-thinking Daniel Vassallo was/is - he’s been advocating one-time (lifetime) offers for years or at least since I started following him, many moons ago. If thoughtful builders like him and the ONCE.com legends (@jasonfried / @dhh) keep pushing it, maybe it does work. Here's another experiment below from someone (@KatieKeithBarn2) in the WordPress niche.

Hey @postmarkapp I have sent you a support request since 2 weeks ago and I have not received any response. It's great sadness to see the quality support of the previous owner and team crumbling like this. Even your chat interaction are all AI now - no human left in your HQ?

@KrisCherukuri This was a good read and resonated with me.

New blog - the visit krischerukuri.bearblog.dev/the-visit/

@nickmdiego I have tried all. Only localwp stands out with some good features. And it installs natively without need to install any docker on the host. Been using it for more than a year now - solid! And if you pair it with the free @wpengine sandbox, great for demo-ing/testing stuffs

Calling all WordPress developers. What's your primary local WordPress development tool? If Other, please note what tool you're using in the comments. Also interested in your favorite features of each.

@BridgetMWillard @bgardner I feel you. Thank you sharing this, Bridget. Sometimes, some dev lack an open mind to listen to others with better "eye sight". Cheers

@wkhayrattee @bgardner The Guttenberg team was excited. I was the head of the marketing team at the time. I knew it would bring breaking changes. The developers I worked for didn’t believe me.

Wow. Eight years of Gutenberg. Hard to believe. 🤯