Yitz Willroth™

41.4K posts

Yitz Willroth™ banner
Yitz Willroth™

Yitz Willroth™

@coderabbi

Coder & Rabbi, async. Former: StartupVet, DevBootCampGuru, Mentor, Consultant, Speaker, Author, ShorePHPFounder, NYPHPOrganizer. Now: Just trying to human well.

I refactor legacy coders.™ Katılım Aralık 2012
1.5K Takip Edilen5.3K Takipçiler
Sabitlenmiş Tweet
Yitz Willroth™
Yitz Willroth™@coderabbi·
@fuelventures Having as much time as I want to sleep, gym, leisure, etc. *is* success.
English
3
13
352
0
Connor Hughes
Connor Hughes@Connor_J_Hughes·
The overwhelming excuse for the #Knicks victory is that the #76ers were "gassed" and had no hope. I could be wrong, but how is the one day off between this one and Game 2 going to magically fix that when there was ... one day off between this one and Game 7?
English
149
158
2.3K
125.8K
Aaron Francis
Aaron Francis@aarondfrancis·
@slaFFik Ugh that's the worst part about being the "single pane of glass" that you run everything in! Updates never come at a good time
English
3
0
2
884
Slava Abakumov
Slava Abakumov@slaFFik·
I'm really tempted to download and update Solo by @aarondfrancis right in the middle of my session with claude. I must wait. But not for long. This tool is transformative to the way you develop things. More on that later.
Slava Abakumov tweet media
English
1
1
3
1.1K
Yitz Willroth™
Yitz Willroth™@coderabbi·
@madsmadsdk @grok We should play! It’s been forever since I’ve been there, but could be enticed to revive my account.
English
1
0
1
9
Yitz Willroth™
Yitz Willroth™@coderabbi·
@TickPick Non-story; ticket sales were zip code locked. You could do NJ & Wyoming and also come up with 56.11%. South Jersey is Philadelphia.
English
0
0
1
418
TickPick
TickPick@TickPick·
NEWS: 56.11% of purchases for Game 3 (Knicks at 76ers) have a zip code from New York and New Jersey.
English
57
103
1.2K
370.9K
Yitz Willroth™
Yitz Willroth™@coderabbi·
@madsmadsdk Either way, you end up with a blocked promoted queen and a rook in the 8th row for the mate.
English
1
0
1
13
Mads
Mads@madsmadsdk·
@coderabbi You’re on to something 👀
English
1
0
1
21
Mads
Mads@madsmadsdk·
This one is easily my favorite chess puzzle. White to move, mate in 2. Can you find it? 😁
Mads tweet media
English
6
0
1
488
Yitz Willroth™
Yitz Willroth™@coderabbi·
@madsmadsdk Up, down, strange, charm, bottom, top -- there is an indie game in there somewhere.
English
0
0
0
9
Mads
Mads@madsmadsdk·
@coderabbi Shit, I forgot about quarks
English
1
0
1
8
Yitz Willroth™
Yitz Willroth™@coderabbi·
@_colemurray prompt engineering ⏬ context engineering ⏬ harness engineering ⏬ scaffold engineering
English
0
0
0
132
cole murray
cole murray@_colemurray·
conversely, i think most teams probably shouldn’t be building their own harness. it is unlikely you will have novel ideas around sub-agent orchestration, compaction, progressive disclosure etc that are worth owning the entire harness spend your time investing in the pieces around the harness: - execution infrastructure - custom tools, MCPs and skills - self improvement on trajectories
Kartik@code_kartik

x.com/i/article/2050…

English
18
7
130
23.2K
Yitz Willroth™
Yitz Willroth™@coderabbi·
The RFC (and the backstory which made it relevant) is inherently political. It has recently been edited by the author to make this more clear, as that was it's real intent. Internals is simply following the process appropriate when an RFC is presented. I would hesitate to paint with a brush that is any wider than that.
English
1
0
0
102
Yitz Willroth™
Yitz Willroth™@coderabbi·
@pronskiy I agree with you 100%. I'm doing some reading between theines, but my guess is that the original RFC sat uncommented upon for a fair bit because many of those active understood the back story without it being explicit in the RFC or internals.
English
0
0
2
196
Roman Pronskiy
Roman Pronskiy@pronskiy·
Quick clarification and full disclosure: I wrote the governance RFC, and I wrote it because the link removal was about to get merged with none of this being discussed. A few things don't match what's on externals.io: The "political exodus" framing came after the fact. Posting stopped in June 2024, no announcement, no decision. Requests to share credentials or set up automation (like Mastodon has) came way before anyone was talking about governance. "Just removing the link, not the presence" — but removing the link is how the project says an account isn't official anymore. The precedent is the real issue: one person stops posting, and a year later it gets formalized as "just a link." No actual decision was ever made. That's why the governance RFC exists. Platform questions, including whether PHP stays on X, should go through a process, not happen by default because someone stopped showing up. wiki.php.net/rfc/social-med… externals.io/message/130719
Yitz Willroth™@coderabbi

- There has never been real governance for those sort of accounts, primarily casual. - Current maintainer is part of the political exodus from X. - Handoff without governance isn't something they wish to do, though seem open to handoff were formal governance established. - RFC is just about removing the link to a now dormant account from the website, not about removing presence from X. - Second RFC underway to establish formal governance. - Once established, ongoing social media presence can be determined and formalized.

English
1
0
18
2.1K
Yitz Willroth™
Yitz Willroth™@coderabbi·
Anyone have (or is) a contract QA Engineer open to a fractional and/or project gig? DMs open.
English
1
0
0
168
Yitz Willroth™
Yitz Willroth™@coderabbi·
- There has never been real governance for those sort of accounts, primarily casual. - Current maintainer is part of the political exodus from X. - Handoff without governance isn't something they wish to do, though seem open to handoff were formal governance established. - RFC is just about removing the link to a now dormant account from the website, not about removing presence from X. - Second RFC underway to establish formal governance. - Once established, ongoing social media presence can be determined and formalized.
English
2
0
3
2.3K
Christoph Rumpel 🤠
Christoph Rumpel 🤠@christophrumpel·
@coderabbi Please fill in on the full story🙏 I want the best for the php community everywhere 🙏
English
1
0
0
328