If you don't mind this unsolicited product-recommendation, I use Kagi now and I'm won-over. Turns out that when users pay for a search-engine it ends-up focused towards the users' needs and not advertisers; funny that.
(Though Kagi isn't perfect: I find it slower than Google: it'll take maybe 500ms for a result compared to <100ms on Google; Search-autocomplete is also less responsive, and their privacy-first approach means they don't save your search-history, whereas I want them to save my search-history for me, but anyway).
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
Woah, that sounds awesome! I'd love to see how you set that up and how much it can do without your intervention/approval for various actions. Might you have a video of your workflow that you could share?
What's the maximum file size for which this is useful in your experience? I have been refactoring some project solely to enable AI code editors to edit it. Some users in the discord suggest a maximum file size of 500LOC or small, which seems unreasonable.
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.
I dunno, I like the simplicity of it, if you have any problems, let's find a solution together.
Compare that to stackoverflow, where you need to first spend 5 minutes studying all the subsites and decide where you try and submit your question, and hope it won't be closed in 2 minutes saying not the right place to ask, not the right format, you asked too many questions too quickly, etc...
I don't think the post or the landing page says anything about solving the problems with software. I interpreted it even more broadly: problems that can be solved by any method
