LogoThread Easy
  • Explorer
  • Composer un thread
LogoThread Easy

Votre partenaire tout-en-un pour les threads Twitter

© 2025 Thread Easy All Rights Reserved.

Explorer

Newest first — browse tweet threads

Keep on to blur preview images; turn off to show them clearly

12. oct-nov '21, crossed the country again with barely any pics: climbed into Joshua Tree, battery caught fire on Apache reservation, blew tire outside Phoenix, rummaged largest motorcycle scrapyard, stayed w family in Texas, doodled the gulf coast, touched the Atlantic in SC

12. oct-nov '21, crossed the country again with barely any pics: climbed into Joshua Tree, battery caught fire on Apache reservation, blew tire outside Phoenix, rummaged largest motorcycle scrapyard, stayed w family in Texas, doodled the gulf coast, touched the Atlantic in SC

energy snob

avatar for hinterlander
hinterlander
Fri Dec 05 15:50:31
I had GPT 5.1 Pro think for 13 minutes on how to convert this post into the most token-dense blurb for your AGENTS dot md file. Here it is:

## AI‑generated Swift/SwiftUI cleanup rules

When editing or generating Swift/SwiftUI for this repo, aggressively normalize code using this checklist before returning changes:

- Modern APIs: replace `NavigationView` with `NavigationStack`; `navigationBarTitle`/`navigationBarItems` with `navigationTitle`/`toolbar`; prefer new modifiers over deprecated ones; prefer Swift Concurrency (`async`/`await`, `Task`) over callback‑style APIs where possible.
- State correctness: use `@State` for local value state, `@Binding` for parent‑owned state, `@StateObject` for long‑lived reference types created in the view, `@ObservedObject` for injected reference types; never create `ObservableObject` instances inside `body`.
- Optionals and errors: remove `!` and `try!` except in truly unrecoverable situations; use `if let` / `guard let` / `??` and `do/try/catch`; surface failures via explicit error paths (result types, error views, alerts) instead of silent failure.
- Collections & identity: in `List`/`ForEach`, prefer stable IDs (`id: \.id` or dedicated `id` properties) over `0..<count` and `\.self` on reference types; avoid recreating collections in `body` when a stored property will do.
- View structure: flatten over‑nested `VStack`/`HStack`/`ZStack`; replace layout built from many `Spacer()`s with alignment, padding, and proper containers; extract repeated subtrees into reusable views rather than duplicating layout.
- Type erasure: avoid `AnyView` and other unnecessary type‑erasure unless you truly need heterogeneous view types; prefer concrete view types and composition.
- Concurrency & threading: mark UI‑affecting entry points `@MainActor`; avoid blocking the main thread; move expensive work off the main actor using async tasks; ensure completion handlers and tasks do not capture strong `self` unnecessarily.
- Side effects: remove network calls, disk I/O, timers, and other side effects from `body`; move them into view models, services, or explicit tasks triggered from lifecycle modifiers (`task`, `onAppear`, etc.).
- Performance pitfalls: avoid creating `DateFormatter`, `NumberFormatter`, random values, and heavy computations directly in `body`; cache in static properties or dedicated helpers; avoid unnecessary copying of large data structures.
- Style & hygiene: delete unused imports, variables, and parameters; use explicit access control; keep naming consistent with Swift guidelines; run code through `swift-format`/Xcode formatting expectations so generated code blends with existing style.

I had GPT 5.1 Pro think for 13 minutes on how to convert this post into the most token-dense blurb for your AGENTS dot md file. Here it is: ## AI‑generated Swift/SwiftUI cleanup rules When editing or generating Swift/SwiftUI for this repo, aggressively normalize code using this checklist before returning changes: - Modern APIs: replace `NavigationView` with `NavigationStack`; `navigationBarTitle`/`navigationBarItems` with `navigationTitle`/`toolbar`; prefer new modifiers over deprecated ones; prefer Swift Concurrency (`async`/`await`, `Task`) over callback‑style APIs where possible. - State correctness: use `@State` for local value state, `@Binding` for parent‑owned state, `@StateObject` for long‑lived reference types created in the view, `@ObservedObject` for injected reference types; never create `ObservableObject` instances inside `body`. - Optionals and errors: remove `!` and `try!` except in truly unrecoverable situations; use `if let` / `guard let` / `??` and `do/try/catch`; surface failures via explicit error paths (result types, error views, alerts) instead of silent failure. - Collections & identity: in `List`/`ForEach`, prefer stable IDs (`id: \.id` or dedicated `id` properties) over `0..<count` and `\.self` on reference types; avoid recreating collections in `body` when a stored property will do. - View structure: flatten over‑nested `VStack`/`HStack`/`ZStack`; replace layout built from many `Spacer()`s with alignment, padding, and proper containers; extract repeated subtrees into reusable views rather than duplicating layout. - Type erasure: avoid `AnyView` and other unnecessary type‑erasure unless you truly need heterogeneous view types; prefer concrete view types and composition. - Concurrency & threading: mark UI‑affecting entry points `@MainActor`; avoid blocking the main thread; move expensive work off the main actor using async tasks; ensure completion handlers and tasks do not capture strong `self` unnecessarily. - Side effects: remove network calls, disk I/O, timers, and other side effects from `body`; move them into view models, services, or explicit tasks triggered from lifecycle modifiers (`task`, `onAppear`, etc.). - Performance pitfalls: avoid creating `DateFormatter`, `NumberFormatter`, random values, and heavy computations directly in `body`; cache in static properties or dedicated helpers; avoid unnecessary copying of large data structures. - Style & hygiene: delete unused imports, variables, and parameters; use explicit access control; keep naming consistent with Swift guidelines; run code through `swift-format`/Xcode formatting expectations so generated code blends with existing style.

Former Quant Investor, now building @lumera (formerly called Pastel Network) | My Open Source Projects: https://t.co/9qbOCDlaqM

avatar for Jeffrey Emanuel
Jeffrey Emanuel
Fri Dec 05 15:50:00
I think there are 2 ways to do it:

1) Hire a specialist, then build out a team around them -- all reporting into your marketing  or editorial lead 

2) Hire a head of social who is very good at the 1 platform where you need to crush it on. Then allow them to build out a mini team of specialists (even if some of them are part-time)

Hiring just 1 Social Media Manager to do it all doesn't really make sense anymore.

Level up or niche down.

I think there are 2 ways to do it: 1) Hire a specialist, then build out a team around them -- all reporting into your marketing or editorial lead 2) Hire a head of social who is very good at the 1 platform where you need to crush it on. Then allow them to build out a mini team of specialists (even if some of them are part-time) Hiring just 1 Social Media Manager to do it all doesn't really make sense anymore. Level up or niche down.

creator & social strategist // ex @a16zcrypto, @linkedin, @snap

avatar for Ish Verduzco 🌐
Ish Verduzco 🌐
Fri Dec 05 15:48:52
Does anyone have a good DevOps flow for Claude Code? 🤔

As in "fix the prod build and verify", it needs to wait 5mins+ sometimes and keep looping.

If multiple things are broken, fix each and try to do it in parallel.

Does anyone have a good DevOps flow for Claude Code? 🤔 As in "fix the prod build and verify", it needs to wait 5mins+ sometimes and keep looping. If multiple things are broken, fix each and try to do it in parallel.

AI Software Engineer | 3x small exits | Side-hustle: 🔊 https://t.co/pRVZEDfsnm $4K ✦ 🎥 Figma Plugin $10k/MRR (sold) ✦ 🕵🏻 Agency $30k/MRR (sunset)

avatar for Michael Yagudaev 🧑🏻‍💻🇨🇦
Michael Yagudaev 🧑🏻‍💻🇨🇦
Fri Dec 05 15:46:00
怎么判断一个人是不是创业生瓜蛋子?

答,如果他在喷网站备案制度,喷 App 上架要软著,喷这喷那,那就是生瓜蛋子。

而且,这种人创业也不会有什么大成就,最多两年就回去找个班上了。

真正创业的人,应该要适应规则生存,而不是乱喷。

怎么判断一个人是不是创业生瓜蛋子? 答,如果他在喷网站备案制度,喷 App 上架要软著,喷这喷那,那就是生瓜蛋子。 而且,这种人创业也不会有什么大成就,最多两年就回去找个班上了。 真正创业的人,应该要适应规则生存,而不是乱喷。

哥飞,出海鼓励师,SEO爱好者,Adsense玩家,出海AI工具方向创业者。 同名公众号写了五百多篇出海搞流量免费教程文章。

avatar for 哥飞
哥飞
Fri Dec 05 15:45:11
«You were saying?»
I'm saying, I get Trump and Vance, I really do. These creatures are to be extracted from and discarded, as that is the only ethos they can comprehend. Let them eat their pizza on ruins of their companies.

«You were saying?» I'm saying, I get Trump and Vance, I really do. These creatures are to be extracted from and discarded, as that is the only ethos they can comprehend. Let them eat their pizza on ruins of their companies.

We're in a race. It's not USA vs China but humans and AGIs vs ape power centralization. @deepseek_ai stan #1, 2023–Deep Time «C’est la guerre.» ®1

avatar for Teortaxes▶️ (DeepSeek 推特🐋铁粉 2023 – ∞)
Teortaxes▶️ (DeepSeek 推特🐋铁粉 2023 – ∞)
Fri Dec 05 15:39:49
  • Previous
  • 1
  • More pages
  • 1501
  • 1502
  • 1503
  • More pages
  • 5634
  • Next