Going to do the same thing. See ya, HN.
1,029 karma · joined August 13, 2010
Going to do the same thing. See ya, HN.
Ethanol has been produced for ages. It is ridiculous and unwise to call it "first-generation ethanol" or even "first-generation-process ethanol". The fact is that they had no green solution for gasoline production, so they used something that seemed green and was much more expensive, then funded the oil companies to use it, but there was no way it was a viable alternative, and it promised to tear up the environment by forcing excessive corn farming for a demand that could never be met.
We need to focus on energy R&D, not stopgaps and unviable energy solutions. In the meantime, if you want green, do everything you can to support teleworking.
I thought that was what security was for, not economists.
https://secure.wikimedia.org/wikipedia/en/wiki/Theanine
and there are supplements available if you don't want to give up coffee.
Why is a resume that shows understanding of the business important? Because it shows that they are focused on what is important to the work and relaying that information, rather than their opinion.
This would be a definite "minus" in my book in a potential employee, unless I was hiring an editorialist. Instead, I would want to see results and understanding of the business. I agree that a resume doesn't do that justice, but it helps when done correctly.
https://github.com/twitter/snowflake/blob/master/src/main/sc...
def nextId(): Long = synchronized {
var timestamp = timeGen()
if (lastTimestamp > timestamp) {
log.warning("clock is moving backwards. Rejecting requests until %d.", lastTimestamp);
throw new InvalidSystemClock("Clock moved backwards. Refusing to generate id for %d milliseconds".format(lastTimestamp - timestamp));
}
Does that mean that the inability to tweet grinds to a halt if the system clock gets set back? That could be a problem whenever the server time is being sync'd with the time server and is running ahead (or if time server goes down/connection goes down- it happens), etc. I know there would be other issues too, but this seems a little fishy.http://www.amazon.com/Nike-Echelon-Padded-Bike-Shorts/dp/B00...
- Get all of the evidence you can that you distributed it first. If this requires contacting another company to confirm records of when you made it available, do that first to have it ready.
- Contact the FSF, send them that evidence, and ask what you can do/should do.
- Send a summary of the evidence you have (or at least some of it, and depending on what the FSF folks suggest) to the person, telling them you wish them to stop selling your script. They will probably stop.
If that doesn't work and FSF couldn't help I'd either:
1. Attack via social networking. Blog, comment, tweet, etc. the hell out of it in areas you know will affect his/her market, linking to your free source.
2. Just give it up.
Good luck!
But, if you really like the opportunity and believe in it, and your family isn't sacrificed, then go for it. You only live once (well at least that's what I believe).
However, you often get what you pay for, and that goes for both hiring inexperienced developers and offshore/contracted development.
If you do hire young/inexperienced, make sure they have a mentor that enforces good practices or have code review/are pairing and that these developers seem to be learning good practices.
There is a difference between bad and "good enough".
- Lots here: http://area51.stackexchange.com/
- Programming, etc.: http://stackoverflow.com/
- Jobs: http://careers.stackoverflow.com/
- Server Administration: http://serverfault.com/
- Web Applications: http://webapps.stackexchange.com/
- Gaming: http://gaming.stackexchange.com/
- Ubuntu: http://askubuntu.com/
- Webmasters: http://webmasters.stackexchange.com/
- Cooking: http://cooking.stackexchange.com/
- Game Development: http://gamedev.stackexchange.com/
- Math: http://math.stackexchange.com/
- Photography: http://photo.stackexchange.com/
- Statistics: http://stats.stackexchange.com/
- TeX and LaTeX: http://tex.stackexchange.com/
- Computer Enthusiasts (OS, etc.): http://superuser.com/
The other two sites are just for support/feedback purposes:
- Stack Exchange API: http://stackapps.com/
- Questions about stack overflow/stack exchange itself: http://meta.stackoverflow.com/
And there are a multitude of other sites that have Q&A, the new kid on the block being Quora ( http://www.quora.com/ ).
oh, we could be here for hours, like Abbott and Costello
- do a survey of customer satisfaction on different points (but make it wide-open so they can express other concerns) and see how well ranking increases or decreases
- do an anonymous survey of employee happiness and self-assessments of productivity (but make it wide-open so they can express other concerns) and see how well ranking increases or decreases
- look at number of requests being served and from where, response times, repeat customers, support requests, errors, etc. (things that people won't hopefully make up)
- look at financials for important parts of the company and how they go up and down
- work hard to put money into R&D, tools, training, maintenance, etc. and take away from parts of the company that are draining money
(sili889q user created one hour ago by notmyname to coincide with his post)
oh no you didn't.
I'm burnt out on programming, mostly because I find joy in business and doing good. I have very little joy in my current job, but I do it because it's my job. I would leave, but I have a family, I don't have income to replace it yet. I want my own successful business, and I'm here to hopefully on HN learn more about that.
I think it would be interesting for someone to do a survey on programming burnout. I know some former programmers, so I know there would be more than people think out there.
These standards aren't really that open because of the committees, large companies, and bureaucracy surrounding them. And major languages we use like PhP, Python, Ruby, Java, etc. (with exception of ANSI C#, Javascript (ECMAScript) and some others) weren't successful because they were based on standards. I use FF (which was touted as standards compliant all during its transition from Mozilla from Netscape) all the time, but if it weren't for Netscape folding and IE sucking, it probably would have had much less market share than it does. I think standards are good, but the red tape slows us down. Put the specs and their reference implementations on Github (if it doesn't go down) and fork them at will, then maybe we'll see some real progress. Successful viruses mutate frequently.