Live data from Hacker News

FarmLogs

blog.samaltman.com

71–80 of 92 posts

Re: FarmLogs

#71
post #68

Earlier quoted context omitted.

Great point. I'm one of the founders of FarmLogs and I can tell you we started this company to help make farmers (like my family) more successful. We don't have ulterior motives with regard to using farmer data. We help them use it to be more profitable and that is all. That said, it looks like we aren't doing a good enough job making it obvious in our ToS. That page has not been updated in a very long time. I am goi…

"...We don't have ulterior motives with regard to using farmer data. We help them use it to be more profitable and that is all." Until the investors/board say otherwise. :) Been there. Experienced it. Resigned rather than comply. Understand FarmLogs is the whipping boy here because you're the thread's subject (and your TOS clause 7 really is scary), but my concerns are also with the others, including for example Deer…

> Been there. Experienced it. Resigned rather than comply.

Not to derail the topic but I'd love to hear that story. Have you published it anywhere?

Re: FarmLogs

#72
post #32

Damn; I wouldn't have thought farmers would be a good group to target software towards, but it actually makes a lot of sense. Out of curiosity, I wonder how these guys actually manage to get those millions of dollars in savings. Nice to see a new startup is trying and succeeding to make a positive difference for some pretty critical customers :) Going to keep an eye on this group for sure. Something tells me they'll…

You'd be surprised - a good friend of mine from high school was from a farming family, and they had a PC in the early 90's when hardly anyone had a PC in rural areas except schools and libraries. (I grew up in northeast Arkansas) They used it for accounting and taxes mostly (and we used it for games!) and they wrote the cost of it off each year. The other major early infusion of tech into farming I can think of is th…

Likewise--my mother was doing our farm's books on an IBM 8088 back in the mid-80s.

Re: FarmLogs

#73
> And importantly, they started out doing something that any two programmers (with domain expertise in their market) could have done.

I somehow remember the original text to be

> And importantly, they started out doing something that any two programmers could have done.

There is nothing on the wayback machine either. Am I misremembering the original text?

Re: FarmLogs

#74

> And importantly, they started out doing something that any two programmers (with domain expertise in their market) could have done. I somehow remember the original text to be > And importantly, they started out doing something that any two programmers could have done. There is nothing on the wayback machine either. Am I misremembering the original text?

I remember it without the parentheses, too.

Re: FarmLogs

#75
post #35

The problem with FarmLogs is the same problem with anyone wanting to provide cloud-based services to agriculture: who owns the data? And specifically, FarmLogs Terms of Service clause 7 "Content" does not leave one feeling warm and fuzzy on this topic. This has become more of an issue with farmers over the past year, as they realize their data is a commodity just like what they raise--whether crops or livestock. How…

"... This has become more of an issue with farmers over the past year, as they realize their data is a commodity just like what they raise--whether crops or livestock. ..." What is stopping a local server/you own the data solution? Is it the cloud solution is the only one on offer or is it too hard to get the hardware/software to the gate?

It's usually too hard to set up such a system yourself.

I'm strongly rooting for https://sandstorm.io/ here - I hope they'll be able to provide a good alternative for SaaS businesses.

Re: FarmLogs

#76
post #68

Earlier quoted context omitted.

"...We don't have ulterior motives with regard to using farmer data. We help them use it to be more profitable and that is all." Until the investors/board say otherwise. :) Been there. Experienced it. Resigned rather than comply. Understand FarmLogs is the whipping boy here because you're the thread's subject (and your TOS clause 7 really is scary), but my concerns are also with the others, including for example Deer…

> Been there. Experienced it. Resigned rather than comply. Not to derail the topic but I'd love to hear that story. Have you published it anywhere?

I second that, I'm intrigued.

Re: FarmLogs

#77
post #35

The problem with FarmLogs is the same problem with anyone wanting to provide cloud-based services to agriculture: who owns the data? And specifically, FarmLogs Terms of Service clause 7 "Content" does not leave one feeling warm and fuzzy on this topic. This has become more of an issue with farmers over the past year, as they realize their data is a commodity just like what they raise--whether crops or livestock. How…

It's good to see that consumers are beginning to question who owns and controls data that is collected from them. I sometimes think that the "big data" revolution is worse than anything the NSA is doing.

Re: FarmLogs

#78
I worked on a sugarcane farm management company a while ago and also built a backbone.js frontend site that tracked sugar cane harvesters and estimated the "outcome" to send trucks to offload it on demand with some colleagues (closed source unfortunately) in resume I like this area very much.

When I saw this post I went running to the Jobs page, and there my heart got smashed when I saw Clojure on backend positions... I am a plain Java dev with learning skills (worked with Groovy/Python/JS a while ago) but I definitely don't like Clojure.

Good luck guys

Re: FarmLogs

#79
post #78

I worked on a sugarcane farm management company a while ago and also built a backbone.js frontend site that tracked sugar cane harvesters and estimated the "outcome" to send trucks to offload it on demand with some colleagues (closed source unfortunately) in resume I like this area very much. When I saw this post I went running to the Jobs page, and there my heart got smashed when I saw Clojure on backend positions..…

It's Clojure not Closure. Why don't you like it?

Re: FarmLogs

#80

Earlier quoted context omitted.

@sshykes, as an employee at Farmlogs I can attest that people here work long hours, if at all, out of their own will. In addition, I have worked at other startups before and I don't think I work super long hours here. There are 5 stars on Glassdoor for a reason. Most of us start late and stay late and love the flexibility in the work hours. Overall, the team really believes that we are building something world changi…

Are you guys at least given the opportunity to work remotely?

Don't work there but applied a while ago. There was interest from FarmLogs until I mentioned I couldn't move there at least for a while. After that email I got radio-silence, so I assume they don't.

ps: not bashing them for that, just giving you a data point

Post reply on HN