763 karma · joined July 18, 2009
https://stepwise.run - Deterministic scaffolding around nondeterministic work. Observable runs. Human gates. Resume after reboot. No babysitting.
https://github.com/zackham/aloop - An embeddable Python agent loop for multi-agent orchestration, declarative permissions, and editor integration via ACP. Use any LLM from any provider, extend through hooks, embed as a library, drive from the CLI, or expose as an ACP server.
zackham@gmail.com
Thank you!
Great movie, though. Amazing to see a popular film come out and do a decent job of portraying a software guy.
I would give a progress bar with semantics specific to what you are doing (step 3 of 5 instead of 60%), estimated time to completion, and a description of the current step (Submitting search request to Expedia... Filtering results... etc).
It can be accomplished a lot of ways, but will likely be more responsive if you push the data. The easiest way I have set up something like this has been node.js, redis pubsub, and socket.io. Requires some reading, but the end result is you can push messages through Redis from your app easily, it will work in all browsers, and you won't have to write very much glue code at all.
var tail = spawn('ssh', ['user@yourserver.com', 'tail', '-f', '/path/to/some.log']); tail.stdout.addListener('data', function (data) { listener.broadcast(data.toString()); });
I did a really simple version of what you're talking about with some client-side parsing of rails logs for fun. Feel free to contact me and I'll be happy to zip up the source and send it your way.
1) You have side projects and experiments that have interesting enough ideas behind them that you think they may be worth pursuing beyond 80%. 2) You think you should be familiar with more than Javascript, PHP, Java, and MySQL. 3) You are not completely happy only being comfortable in a Windows XP environment with whatever IDE you are using.
Each of these items has a clear next step. (1) Think about your projects, pick your favorite one, look at the code and do something minor. (2) Poke around and do some light research (if you haven't already) on other dev stacks, play around until you find yourself genuinely interested in one. (3) Install Ubuntu in a virtual machine (VirtualBox is free and works well) or dual boot. Google vim and emacs and pick one to start playing with.
If you feel like you are falling behind you can use that as an opportunity to figure out what you're unhappy with specifically and do simple things to take a small step forward. You can't do everything all at once, and the people here that are impressive to the point of it being intimidating got where they are by diligently making incremental progress over some time.
Will probably end up with another monitor here soon, just haven't decided if I should get another 24 or something smaller that I can run vertically.
Here is a thread where people are talking about using the Seidio 1750 mAh in their Evo: http://androidforums.com/accessories-evo-4g/88887-seidio-inn...
And here is an older comparison of OEM and 3rd party batteries with disappointing results: http://www.batteryboss.org/
Nice recap of details I had read a bit of a few years ago... also, highscalability is a great blog that is likely of interest to many HNers.