tangled.org/nvim-mini.org/mi…
nvim 을 mini.nvim 기반으로 리셋해볼까 하는 생각도 든는 밤이다.
1
55
anarcher retweeted
Can't believe I once spent a summer trying to learn Vim.
Future generations will never know the anguish.
rex도 lua script 이고 nvim도 lua script.
xitter.cf/almonk/status/21230444…
posted this into our Rex discord today... the new `𝚛𝚎𝚡.𝚞𝚒` primitives provides a new set of simple but powerful methods to build interactive scripts within Rex that require user interaction.
Now you can build the workflow of your dreams, that little action you always wanted or just a pizza topping selector.
I wrote some docs up that go into detail about how this feature works superlogical.com/rex/docs/cu…
101
레인메이커 재밌게 보다. 오랜만이 법정낭만극 본 느낌. 소설을 잘 현대에 맞게 각색한듯. “나의 최악의 자질은…” netflix.com/kr/title/8213722…
117
anarcher retweeted
🔪 "기술은 그 자체론 선도 악도 아니다, 쓰는 사람에 달렸다?" 흔히 듣는 말이죠. 이를 '기술의 가치 중립성'이라고 합니다. 하지만 과학기술사회학(STS)의 시각은 다릅니다. 기술은 단순한 도구가 아니라, 그 자체로 사회의 편견과 권력이 묻어있는 '정치적 산물'입니다. 🧵
anarcher retweeted
Appreciate it! I think I speak for everyone at Superlogical that we’re tired of software that feels like demoslop and we’re motivated to show the world what meticulously crafted software feels like again.
We use AI of course, but showing the difference between tasteless prompting and a team of experienced craftspeople enhanced by AI. We hope!
Rex by @superlogical is phenomenal software. tremendous fit and finish, feels like it was built and designed pre-AI (compliment)
anarcher retweeted
I support Jensen Huang's reinstatement at Nvidia, and have signed the public petition addressing that.
If Huang colluded with a Chinese spy he should be punished with the weight of the law. Otherwise, the only person wronged in this mess is his wife, and it's up to her to decide what to do about that, not Nvidia's board.
Yes, he screwed a subordinate. I would ordinarily view that very seriously, but my understanding is that the woman is independently wealthy due to Nvidia stock appreciation and thus not really coercible. It's not a simple question who is using who in situations like this.
But the most important reason I support his reinstatement is because he is one of the most powerful people speaking in favor of open-weight and open-source models, and against an idiotic and self-destructive "AI pause".
This technology will either empower everybody or usher in the most grinding totalitarianism the world has ever seen. I know which side of that I'm on, and I think I know which side Huang is on, too.
anarcher retweeted
Replying to @valigo
Most people have no idea what ART is.
As soon as you phrase it as:
The art of science
The art of programming
The art of painting
The entire concept usually becomes clearer. Art isn’t a category of objects but a process.
요즘 rune.build/ 도 사용중. 바이브 코딩의 시대이라서 예전보다 에디터를 적게 사용하긴 하지만, vim 다음으로 rune이 키보드 퍼스트 인터페이스이라서 이해하기 어렵지 않았다. 특히 vim preset이 있어서 vim 키맵을 사용할수도 있다. Ebitengine(2D엔진)기반 UI도 특이하다.
1
5
286
한글 입력안되어서 PR 보냈는데, 머지 되었다. github.com/unstablebuild/run…
39
AI시대에서는 (오히려, AI에게
얻을수 없는 가치인) 좋은 문화를 가진 팀이 더 잘 될것 같다.
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work.
First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs.
Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue).
Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main.
Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown.
The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in.
Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way.").
This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours.
All of this works on mutual trust. It ONLY works with mutual trust.
Everyone at all times has to trust that they've got each others back:
1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts).
2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer.
3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly).
We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago.
In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
4
259
















