Reminds me of similar work at Google to take natural language commands e.g. "Put the soda can on the table" and make a LLM write lower level robot code to implement the task. https://code-as-policies.github.io/
Greenhouse Software | New York, NY | ONSITE | Senior Full Stack Software Engineer
Software engineer at Greenhouse here. We just opened up a new role on our product engineering team. Come join our team!
Learn about our engineering culture here: https://engineering.greenhouse.io/ (fun fact: I'm in one of these photos, can you guess which one?)
Greenhouse builds world class recruiting software. Startups in this thread (see the links that have the ?gh_jid= querystring param) as well as top companies like Airbnb, Twilio, Lyft, Betterment, and ThoughtWorks use our software to optimize their recruiting processes.
Greenhouse Software | Software Engineer | New York NY ONSITE
Software engineer here. We're looking for someone to join my team -- Solutions Engineering. If you have experience building APIs, let's talk!
You'll spend a lot of your time working with our customers and building robust APIs for them to use. It's a Rails shop here, but no experience with Ruby or Rails is necessary. I'd recommend a few years of backend web experience.
I work at Dwolla. Just want to say that I personally agree with you that clarity around pricing is important for any open platform. Especially when you're comparing a product or service against competing options, concrete pricing is key.
As a developer hacking on a small project, there isn't any cost to use our network. If you're a merchant accepting payments on our network, we'd like to see you enter a package once your business starts to make several hundred transactions a month, but we don't require it. Most businesses end up wanting more advanced features once their volume goes up. The cost of those premium features will depend on your volume and needs. As we learn more about what works best for our partners, I think we'll be able to provide more pricing information up front.
We appreciate your feedback. Our product team will continue to work on providing clear pricing options.
So you want to answer the questions 'when did i fall sleep last night?' and 'did i get enough sleep?' I have to wonder why.
It suggests you are wanting to ensure you get a healthy amount of sleep by getting the answers to these questions. But really, you don't need to answer these questions at all. Instead just time-box the amount of sleep you should have (whatever you determine that to be) and then just set alarms on your phone/laptop around your schedule to instruct you when to go to bed and when to sleep - sorted.
I sense your overly elaborate, approximate solution to your problem is a result of you suffering from sleep deprivation! ;)
Yes. node-webkit / nw.js is really slick. I love that I can create a desktop app without even a hint of Cocoa or Obj-C on my part. The runtime is like 90mb, yes, but the source itself is 4mb including dependencies. Memory usage is decent at ~18mb
I don't know about you, but I don't want an applet as small as this eating up 18MB...
Really, what's up with you people?
BTW, not saying that the idea is bad or anything, but it's sad to see people talking about such a waste of resources like it's OK to use in "production". People have other stuff running on their machines and it adds up, quickly.
> The runtime is like 90mb, yes, but the source itself is 4mb
Not to be too acerbic, but, first of all, 4 MB is already huge for an applet. Secondly, how does the fact that the source is 4 MB excuse the 90 MB runtime?!
