skysight-inc/HackerNews huggingface dataset:
Yay - designer/developer "teams". Sounds fair enough, but it's gotta work both ways.

You as a designer need to be flexible. If I as a developer say "that can't be done within the given time/budget/constraints", you'll need to rework or rethink some of your precious design.

I as a developer need to sometimes do some more research to make sure something can, in fact, be done, instead of relying on 10 year old preconceptions about what's possible and what's not. I may need to tell a client/pm that we're going to do XYZ visually and IE5 be damned because I've looked at the stats and 0.21% of the visitors in the past 18 months used IE5.

I've rarely seen true teamwork collaboration between designer/developers in the web world, and it's worse in the 'virtual team / freelance' world, because pretty much every project is a new set of people working together for the first time.

What's more common is a designer puts together some graphic design which is fairly impossible to recreate in browsers, then complains tirelessly that it doesn't look exactly 100% the same on every single browser, including their WAP phone, iPhone and IE6 on XPsp1, and proceeds to tell you about their cousin who made all this work perfectly 6 months ago because he wrote some javascript to make everything awesome. Then the designer coming back 4 hours before a demo/launch and telling you that the color in the footer on each page needs to be different, but they're going away on vacation in 10 minutes and "it's pretty simple, just look at the 19 mockups I emailed to you in February" (conveniently named 'XPJ59 client X here's slide #1.JPEG', etc).

Also more common is a developer who takes no notice of the designer mockups that were approved by 8 people over 2 months, and just does their own thing with CSS3, custom modified jQuery, and only tests on their custom Konqueror or Chrome beta release, then pushes to Heroku where only they have an account and rights to push.

Yes, designers and developers need to learn to work well together to appreciate the issues each faces. Web designers do, in my view, need to have a better understanding of web technologies, understanding the limitations and possibilities of the tech. I don't see how you can do that without actually, you know, learning how to code some. Developers should have a better idea of how to use graphic tools, and sit in on some meetings where designers are subjected to idiotic whims and endless debates on shades of blue to have a better understanding of why the designer is bitching about what should really be a 2 minute change for the dev (cause the designer will get it in the neck from 8 people if they don't).
Meebo Ads Privacy | meebo
Make your mousetraps stronger, and the mice will evolve better muscles.
Fujitsu Develops World's First Cloud Platform to Leverage Big Data
I was there a few months ago. While tourists were swimming, Filipinos were all floating with life jackets.

It surprised me that, in a country that is basically a cluster of small islands and where you can only get around by boat, nobody can swim.
I typically use master for developing, and another branch called "production" to store whats live.
Alas, it's woefully short on any real technical detail.
Agreed, and there are many cases where a robot will remember to do such things for me before I will even think about it (artificial intelligence) whereas I may forget to book my ticket, or I may look in my refrigerator at dinner time just to see it is empty.
Honestly, going in as the first employee of a startup shouldn't be a decision made by someone just looking for compensation. Rather, a first employee should be someone who is so hooked on the idea of that startup, they focus on the ability to build a company from the ground up. It's a risk, but if all else fails, they can find a job working for an established business that can offer those numbers. Joining a startup early on should be based on beliefs and passion for the company, not a paycheck.
I think in state machines all the time, and I have it second hand that telecoms services in South America mostly run on state machines.
WRT your side note Wikileaks apparently hold data that could embarrass many governments and hurt many corporations. Really you'd have to ask which countries and global corps don't have an interest in getting inside Wikileaks.

Have Wikileaks sought investigation of DDoS attacks, I'm going to guess not. I think the FBI would jump at a chance to investigate the internals of Wikileaks to work out were attacks are coming from - for many reasons. Whilst PayPal are being directly financially affected and, on the other hand, are extremely likely to have reported and sought investigation of every instance of substantial cyber attack against them.
I am editing a forthcoming book in the field, written by a teacher who earnestly believes in MI. Evaluating this teacher's data, his approach is clearly working for his students, but I think because of better engagement, more individual attention, and more interdisciplinary projects. Ultimately, I think we're cutting most of the MI stuff from the book as unsupported, although he will cite Gardner as inspiration.

The data I've looked at is more consistent with variation in subject performance primarily correlating with interest and personality, rather than MI.
Sure, not everyone agrees with his theory. However, that's not the point of the article. :)
Como perder kilos a través de dietas y ejercicios 
Esta buscando un metodo efectivo y saludable para perder eso kilos que tenemo
demas consurta esta pagina donde te recomendamo una dieta saludable convinada
con actividade fisica.Con el fin de deshacerse de la grasa
Premature Scaling Kills Startups
"The team of the digital era is a designer / developer team"

At my last job, I kept trying to get them to hire a designer. When I left, there were like 15+ developers and no designers. A couple of them thought they had designer skills, but they didn't really. They ended up outsourcing their design, and of course, a lot of back-and-forth was needed.

I absolutely think that designers and developers need to work closely together.

I also think it's -possible- to have someone who is great at both. But you're going to pay them a lot more. Probably more than having 2 specialists. They are going to be amazing at what they do. You certainly won't get twice the work from them that you get from 2 specialists.
Be authoritative to stay DRY
LoseThos is for programming as entertainnment. It was common for one person to make games on the C64. Obviously, that person was a programmer, not an atrist. The poor resolution and colors made an even playing field -- it all looked primative.

Don't worry -- all those extra pixels you're missing in LoseThos would just have made making art more tedious.
Show HN: FBSE: EmpireAvenue competitor written in node.js for the node knockout
Hsoub Ads, Contending for Arabia
FSMs are very common on the embedded systems I work on. In fact, I often find that my coworkers use them too much. For instance, sometimes a DSP filter would be a much cleaner and maintainable solution. That said, if you work on embedded systems and you've never used a FSM, you're probably doing it wrong ;)
State machines are a form of declarative logic as opposed to procedural, and declarative is often superior for modelling real-world activity.

Procedural logic tends to be brittle - small changes have unintended consequences. Declarative models tend to be more robust and, especially with domain-specific languages, safer for domain experts to manipulate. You can certainly design domain-specific languages for the subset of declarative systems that are state machines.

I've happily used state machines in enterprise projects. One was tracking rates of financial instruments, where they would be in various states of validity (i.e. is it a live offer?). Another was a logistics app, where data would move through various states of being cleansed and approved, or rejected. We built a UI around it. By isolating the state definitions and their transitions, it was easy to validate the program's model with business exprts.
Book review: Eloquent JavaScript
FedPlatform.org Focuses on a Government PaaS
Simple, because most developers are not computer scientists i.e. no formal training in finite automata, computability, complexity, nondeterminism, regular expressions, non regular languages, context free grammars and languages, Turing machines, halting problem and underlying math in general.

If they did, trust me they would use state machines without too much reservation where appropriate. But as it is, the concept is foreign to most and good ones intuit their way into implementing one perhaps (just guessing here).
I've created PostCatcher - the HTTP POST requests testing application

Check it out at http://nko2-3node.herokuapp.com
I've been adding a state machine whenever I find myself adding a state column for a couple of years now.

I have always found this streamlining at least one change in the couple of months after initial implementation.
> Now you can argue that cash is 'fungible' and how the real value comes from the employees - blah blah blah the market says otherwise.

"The market says x so it must be true" is a lousy argument. Markets get distorted all the time by unequal bargaining positions, one side having better information than the other, etc.

If markets were even close to accurate, consider that the range of pay for professional software developers would vary by at least a factor of 10 just around the middle of the bell curve. And if you're hiring employee #1 to join a small team of founders, you want someone who is at least at the top of that range.
How many startups end up being the next Microsoft or Google? With this kind of reasoning, buying lottery tickets would be a sound investment: Look at those guys who won 100 millions!
Why I hate error codes?
Node.js ko entry: heatwave
^^ This. Plus, the employee is coming on AFTER a substantial fund raising round, and should not expect the same terms since the company is already validated (and capitalized); thus, the "investment" risk is reduced.

I also agree with the other posters: "paycheck" employees are not good hires early on in a startup.
Why Governments Don’t Get Startups
I disagree. Just to be clear, we're talking web design here in HTML/CSS, not actual programming in JavaScript or Ruby. HTML/CSS creates designs, just like pencils create sketches and paint brushes create painting. Sure, it's hard, but watercolor and oil painting is also hard and has to be learned. Web design is no different.

IMO, in a team, creating the HTML and CSS is a responsibility of the designer. The developers are too busy doing real coding. At least, that's how it works in the design agencies I know personally. It's always a designer that creates the markup, whether a lowly design intern or a production artist. Maybe enterprise and tech startups are different, but that's how it works in the design agencies.
I'd call it a feature, not a bug
JavaScript and DOM API fuss
Yes... a flat density statistic is fairly useless to describe somewhere like Britain, although perhaps it is a weak proxy for relative density, because most places will have density variations.

p.s. did you just walk around in a circle, though?
Sandboxing JavaScript
One more proof that startups are for people that are into the experience. Not the money, not the credit, just the fun of doing it. If you're about calculating your percentage, figuring out if your're getting paid the largest sum of money around or have the best title - talk to the recruiters of big cos.
The jobless recovery is no recovery…
Thanks for clarifying your question. So, if I get it right this time, we're talking about the design of the behind-the-scene stuff (code), regardless of the appearance.
Definitely, the code on the left appears to be a better solution. At least, since "your code is my hell", I'd rather be presented with the code on the left.
But, as you know, there are ways to encapsulate the code on the right so that it is exposed just like (or pretty close to) the one on the left if you really need to.
You're right. Every discussion about "designers should code" always shows problem in teamwork and communication, not in coding skills. :)

And even if as I was saying learning to code is a way to create these skills, like designing things is for developers, another way is just listening to the developers/designers in your team. It works very well and it's way more efficient for a lot of different people. :)

Teamwork, and trust.
> The employee invests $136 each day with the option to leave and cut their losses anytime.

(a) That depends on where you are.

(b) You are ignoring the opportunity cost to the employee (though admittedly this is consistent with the original article).

(c) You are ignoring the potential adverse consequences on the employee's future career of being associated with a failed start-up, leaving a job early to chase dreams, etc. (Please don't tell me that it's better to have a CV showing you worked at several failed start-ups than it is to have a solid track record of demonstrable good results at established companies. That is the kind of fiction that only people in the start-up community manage to believe.)
I think something is being overlooked here. As a designer, when "learn to code" is suggested, it's not aimed at programming languages (C, Ruby, Python, etc.), but rather simple/easy to understand things like HTML/CSS. Any self respecting designer should be able to take a .psd and get it working in a browser. And although it's not necessary for a designer to understand development languages, there's nothing wrong with it (regardless of scientific theories).
YYRRR
Going on a tangent here.

While programming is certainly the most marketable skill of a computer scientist, computer science is not about programming. Computer science is the mathematical study of computation; it's the study of processes and of information. It is possible to be a great computer scientist without knowing how to program.

This doesn't excuse the university of Rwanda: programming is possibly the best tool we have to teach CS these days, and it is a skill that most computer scientists should grok. But I do think a CS degree's value is not only measured by how good a programmer it means you are: CS is a scientific field, not engineering.
Design is not about the tools you use, and development is not about the code you write.

Developers can learn design fundamentals (and I mean really basic "what's the idea behind this color/element/typographic decision?") without touching Photoshop, Illustrator, etc.

Similarly, designers can learn about what is and isn't possible, without learning to code, through research about the existing technologies and their use cases.
Yeah, that caught my eye too. I was waiting to see if there was any engineering or science degrees in the group they selected but nope. All BAs.
I agree with you, what's next after this? designers that can't use photoshop because it is not part of their intelligence type? HTML/CSS is the designers medium and they have to learn how to use it just as a painter needs to learn how to use paintbrushes or a film director needs to learn how to use a camera.
This covers the equity issue pretty well:

http://www.bothsidesofthetable.com/2009/11/04/is-it-time-for...
This should be a feature they offer to all of the Alexa top 100 websites.
Agreed, although "just listening" doesn't go as far as "just listening while also having walked a bit in their shoes, or at least tried those shoes on for size."

I saw a presentation by a designer/developer team a couple years back - one blog entry on that is here: http://www.viget.com/inspire/stop-driving-your-developers-cr...

Another here: http://www.viget.com/extend/stop-pissing-off-your-designers/

And slides here http://www.slideshare.net/mindywagner/10-things-designers-do...
Leaving aside that 1% is, in reality, too small a % for employee #1 of most startups, there are two factors that might make it worth it:

1. Route from employee #1 to v. senior position (with commensurately higher salary) is shorter* irrespective of whether the employee stays with the startup or moves on. (*Shorter than if the employee was working as a small cog elsewhere), and thus there is a fairly strong "jam tomorrow" argument that can be made.

2. Route from employee #1 to owning your own funded startup is again shorter. As employee #1, if you do a good job, then you'll be considered a de facto founder, and thus will have that to add to your pitch when it is your turn to try and raise $500k.

A third factor is that money is not everything. Working for a startup can be awesome, and might give you a whole range of professional and life experiences that you would not get when sucking down at your $100k pa teat.
The Fundamentals Of The Math Behind 3D Graphics [pdf]
it's amazing, how many web forms still suck, as if the web was just invented yesterday.
Intel Invests In Device Security Startup
How to stop a coffee ring from forming (kinda)
I will call your bullshit and raise you a fallacy. ;) But seriously, I think that pigeon-holing yourself into one skill set is the WORST thing you can do. If nothing else, you should at least attempt to learn code so that you might be able to produce reasonable, efficient designs that the coders can easily implement.

But it goes much farther than that.

Someone (on the internet) once said "programming is the new literacy."

I am both an artist and a programer. I am not very good at either, but I find having a knowledge of both is extremely empowering. I DO NOT believe that you are born an artist or programmer. Sure, you might be born with a slightly better brain than the next person, but anyone with an IQ above 70 can learn to program and/or draw. Learning both is not time wasted, but time invested. Being a good programmer can actually save you time as a designer.
After working for a startup, I'll never work for another one unless I own at LEAST 50% of it.
4 Sites to Submit your Start-Up to
sure, but you can have belief and passion and still not want to be screwed over financially.
SproutCore has an entire statechart framework built into it. Not sure where the OP is getting his data...
I had the same reaction. Almost nothing but FSMs in game AI. Makes me wonder if we need to look beyond FSMs for the next level of intelligence.
I (as a Java developer) use state machines often - and know other developers who do same too. I use mostly enums (though there are other ways of achieving it), as explained in this post:

Java Secret: Using an enum to build a State machine: http://vanillajava.blogspot.com/2011/06/java-secret-using-en...
Game prototyping with JavaScript & CSS3
i am not saying git is insecure - i am saying someone needs to do exactly the analysis you are sketching. you can wave your hands and say that this is not a problem, but it's been 6 years since sha-1 was broken and that's an awfully long time.

also, i find it absolutely typical of the place that HN has become that my original post asking a reasonable, informed question with reference is voted down. you're a bunch of mindless fucking morons.
He talks a lot about luck, but I think the better your skills, the less luck you need.

I've noticed that the great writers don't talk about luck, but they DO talk about writing a lot before they got published. I just looked up Stephen King and he started avidly writing at 12, started sending to magazines at 16, and got published when he was 20. That's a lot of writing. Source: http://www.horrorking.com/interview9.html

But for us normal people who aren't giants, luck will be needed to find just the right conditions to get published.

I do think this somewhat applies to programming as well, especially game programming. You can't just jump in and have your first game be an overnight success. You need to practice for a while, write some mediocre games, and then finally get your stride and start turning out gold. Luck is still needed, though.

Minecraft is a good example. It was a relatively unknown game. Then one day it got published in a magazine, the internet got ahold of it, and it blew up. It was still exactly the same game as the previous week, but now it was popular and famous and selling like hotcakes. Not that it wasn't a good game... But without luck (getting published in a magazine) it wasn't going anywhere.
Agreed. One of the biggest intangibles of being an early employee is the amount learned, which (I imagine) is better than the learning for an investor.

The path of early employee => founder is pretty well trodden. Aaron Patzer of Mint and Drew Houston of Dropbox are two immediate examples that come to mind. Who else am I missing?
HTML5 game: Adslife
here's a blog post Moxie wrote that explains "Trust Agility":
http://blog.thoughtcrime.org/ssl-and-the-future-of-authentic...
Sage: Creating an Open Source Alternative to Maple, Mathematica, and Matlab
True, it's better to have a set of states instead of a dozen boolean values. It gives better code, and better organized databases too.
Not entirely an accurate depiction of equity calculations, but it is nice to see as many people as possible doing these back-of-the-napkin sketches to educate. Mark Suster has some great posts about equity math.
I hope I didn't just get screwed then..I've been given 1.5% equity as a first employee, with an option to get additional 1.5% over the next 9 months (0.5% every quarter). With a salary of 65,000. I'm the web programmer developing the product from the ground up. We haven't yet raised any VC money, it's self funded by the 2 co-founders, one of which is a doctor who is primarily the finance arm. Did I just seal my fate? I'm 22 and have not dealt with being part of a technology startup so I wasn't really sure what percent equity was fair. I believe my shares won't get diluted with investment rounds based on the paperwork that I signed though, they're preferred as opposed to common, if that makes any difference?
Ask HN: Who is Hiring? (September 2011)
Please lead with the location of the position and include the keywords INTERN, REMOTE, or H1B if the corresponding sort of candidate is welcome. Feel free to post any job that may interest HN readers from executive assistant to machine learning expert to CTO.

No recruiters or job boards, thanks

Ask HN: Freelancer? Seeking freelancers? (September 2011) http://news.ycombinator.com/item?id=2949790
I've always used a state machine whenever I've parsed XML using an event based parser (SAX).

Although lately I've been replacing an explicit state variable with a stack containing the current element path, since that's pretty easy to do using modern languages.
"How much do you want your monthly payments to be?" -Car saleman
Ask HN: Freelancer? Seeking freelancers? (September 2011)
Please lead with either SEEKING WORK or SEEKING FREELANCER, your location and whether remote work is a possibility.
Yeah, that's a huge collection of communication problems, great. Exactly on spot. :)
I agree with the discussion here. State machines are very useful. The best thing about them is how easy they makes documentation. You just draw a state diagram and you're done!
At least he got offered equity. The first one I joined didn't even have that.
That looks neat, but I have no reason at this time to trust this project over some random CA.
Monkey patching, subclassing, and accidental overriding
You just gave me a flashback to Lucasarts, circa 5 years ago.
Karlsruhe, Germany - mSALES GmbH - Ruby Developer

We're looking for a Ruby Developer (preferably on site, german speaking)

http://www.msales.com/jobs/ruby-developer (in German)

http://goo.gl/DeBp1 (the above in English)
If the startup isn't considering their first employee a crucial hire then they're doing it wrong.

And if you, as a job seeker, are dependent to land a potentially low-paying job at a startup to get a "real" job, then you probably aren't that "crucial hire" the startup is looking for.

This ain't no charity business.
"tipped labor must be paid a minimum of $2.13 per hour, as long as the hourly wage plus tipped income result in a minimum of $7.25 per hour." [1]

[1] https://secure.wikimedia.org/wikipedia/en/wiki/Minimum_wage_...