Weโre honored to share that Planetary Talent has been named 2026 Kansas Tech Startup of the Year by @FlagshipKansas
Weโre proud to be building here in Kansas, with an impact world wide. Thank you to Flagship Kansas for this recognition.
Ad astra per aspera ๐๏ธโจ๏ธ
also for small teams don't be afraid to explore custom solutions! with claude i find it is just as easy to roll your own than it is to integrate and pay for a service you hardly use
and waaay more enjoyable
one of our core tenants at @PlanetaryTal is creating joyous experiences. we believe in beauty as much as function
that philosophy even extends to internal tools like a custom logging solution!
thereโs no need for a log viewer to look this beautiful, but it gives me an irrational amount of joy each time I log into it
and therefore, it is totally worth it ๐
one of our core tenants at @PlanetaryTal is creating joyous experiences. we believe in beauty as much as function
that philosophy even extends to internal tools like a custom logging solution!
thereโs no need for a log viewer to look this beautiful, but it gives me an irrational amount of joy each time I log into it
and therefore, it is totally worth it ๐
We can neither confirm or deny, at this time, the latest leaked images of the planned @NASAMoonBase featuring a Planetary Talent outpost.
Follow official channels only, and please stop sharing the attached image on social media. Thank you. ๐ @NASA
Woke up to this incoming transmission to my iPhone receiver this morning. ๐ฅน๐ก
This is why we do what we do: match the perfect person to the perfect role.
re: agentic engineering, vibe coding
I'm now fully convinced complex hooks, custom skills, plugins etc are a compete waste of time. Your codebase is the context. Agents will discover your conventions and the right files through their own exploration.
The optimal workflow is just having a conversation with your agent, describing what you want, pointing it at a few files, and sending it off. Use worktrees if you're worried about multi agent collision.