anarcher (@anarcher) header
anarcher (@anarcher) profile picture

Somewhere between machines and people. Less is exponentially more. Deciding what not to do is as important as deciding what to do. 靑天亂流.

seoul,korea
Joined May 2008
Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)Photo by anarcher (@anarcher)
언어로 설정을 하게 되면, 규율이 필요하다. 흠.. 어찌보면 yaml의 장점은 부족한 기능 때문일지도..
22
Can't believe I once spent a summer trying to learn Vim. Future generations will never know the anguish.
87
9
12
343
26,855
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
에이전트로 바꿔 읽으면 될까…!
• 『코스모스』의 칼 세이건이 존경한 작가 아이작 아시모프의 전설적인 대표작 • 현대 인공지능 윤리의 모태 '로봇 3원칙'을 확립한 전설적 SF 시리즈 • 1990년대 비공식 번역본으로 유통되다 절판된 후, 첫 정식 완역 🤖 「로봇 시리즈」가 황금가지에서 출간되었습니다. ※ 정보라, 이영도, 김보영 작가에서부터 하세훈 로봇공학자까지, 국내 주요 필진 9명의 「로봇 시리즈」에 관한 에세이 책자 수록. (세트 구성 한정)
3
186
점심수다로 이 이야기 했었… 남송이 중국의 르네상스이고, 조선이 우리의 르네상스이었던 이유. 성리학과 과거제도.
세습사회로의 회귀. 송나라의 과거제도는 능력과 노력으로 자신의 운명을 바꿀 수 있다는 희망과 동기를 부여했다. 하지만 몽골의 원나라가 지배하면서 기회는 능력보다 가문과 혈통, 그리고 지배층에 대한 충성에 따라 주어지게 된다. 그리고 그게 우리가 맞이할 미래다.
2
237
anarcher retweeted
🔪 "기술은 그 자체론 선도 악도 아니다, 쓰는 사람에 달렸다?" 흔히 듣는 말이죠. 이를 '기술의 가치 중립성'이라고 합니다. 하지만 과학기술사회학(STS)의 시각은 다릅니다. 기술은 단순한 도구가 아니라, 그 자체로 사회의 편견과 권력이 묻어있는 '정치적 산물'입니다. 🧵
3
447
18
586
28,507
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)
148
105
22
3,103
131,665
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.
67
176
11
1,872
27,849
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.
9
6
251
4,648
LibreOffice actually works 365 days a year. Just saying.
1,278
12,080
1,223
93,871
1,793,011
흑흑 Rust 배워야 하나. (이 말을 백만번은 한듯)
1
1
308
어찌보면 지금이 공장형 수공업 시대이었을지도 모르겠다. xitter.cf/anarcher/status/212106…
Replying to @anarcher
그전까지는 공장제 수공업있었는데, 러다이트운동은 모든 기계를 반대하지 않았고, 숙련공의 몰락을 가져오는 저품질 대량 생산 기계만 반대했다. 그때는 사실상 노동자는 투표권이 없는 사실상 영국은 귀족민주정인 상태.
111
러다이트 운동의 Luddite는 네드 러드(Ned Ludd)라는 사람이 주도했다고 해서 러다이트의 운동인데, 실존 인물인지 모른다. 공장 기계가 망가졌을때, 가상의 네드 러드가 그랬다고 변명하는 유행 혹은 밈에서 유래 했다는 설도 있다.
1
162
그전까지는 공장제 수공업있었는데, 러다이트운동은 모든 기계를 반대하지 않았고, 숙련공의 몰락을 가져오는 저품질 대량 생산 기계만 반대했다. 그때는 사실상 노동자는 투표권이 없는 사실상 영국은 귀족민주정인 상태.
1
170
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
anarcher retweeted
다정하려고 노력하는 사람이 좋다 다정하려고 노력하는 그 마음마저 이미 다정한건데
9
5,196
586
18,269
413,572