viewhub

Cool. I'll take the API for a spin in the next week. If I use it for my upcoming project, I'll need the ability to control the available CPU/GPU/Memory attached to each sandbox so I can right-size it for the workload. Congrats on the launch!

What compute resources does the sandbox have? Memory/CPU/GPU?

Definitely LOL'd watching the video when it opened up with the singing native American trope. Marketing content is torture. I'll die on this hill.

Sure, I'll record a little something with Loom for you tomorrow.

Windsurf + Haskell w/ CLI tools has been pretty amazing. Windsurf's agent will loop for minutes on its own to figure out the right structure of a program. You just need to tell it to:

- use the hoogle cli to search for the right types and functions

- include a comprehensive test suite

- run a build after every code change

- run tests after every successful build

GHC + a Claude-based agent is a thing to behold.

Try to reduce the number of required sync meetings in favor of async alternatives. For the required sync meetings, make sure there is a rock solid agenda and EVERYONE knows what is expected from them going in. Make sure the meetings cover meaningful material and helpful to all attendees. Encourage everyone to speak up and contribute. If you find certain individuals not contributing or not prepared, proactively have a conversation with them outside the meeting to reset expectations.

For async communication, it can still be helpful to set specific windows of time for things to get discussed. Example, Mondays 9am-Noon ET we review/discuss sprint goals. I like to record short videos with Loom to kick off discussions like this. Make sure to center these types of communication around specific tools, e.g. JIRA, Confluence, Google Docs, etc. Make sure the discussions convert to traceable decisions in your tooling.

Massively agree with this. It can be difficult to create a culture where everyone talks in the open but it can save so many little and big mistakes!

What's your stack? What type of response times are you looking for?

Shrink your market. "Problem" is too open-ended. You can't possibly make effective software for all things.