Hacker News Reader

andhof-mton Why Code Snobs Are Invaluable

But your thinking like a programmer. Some times it is also valuable to think like a business.

What is the goal of this software? Ship now? MVP?

Are we trying to polish the software? Or just get it to work? Is it a prototype?

Some thoughts to take into consideration.

andhof-mton The birth of Microsoft's new web rendering engine

Browser war? Sure.

But regardless of the improvements MS makes, they still have years worth of a bad reputation they have built up to get over.

It will take leaps and bounds for them to ever build up the respect that Mozilla and Google have for building web technology.

andhof-mton Richard Hamming: Learning to Learn

One of my motivations in building videos for: https://www.youtube.com/user/devfactor

Was just this. In school you can listen, and be taught. But learning how to learn is an entirely different skill. Foundational knowledge is really important, but eventually you need to know how to pick up things on your own.

Understanding the learning process, and the process of seeking out relevant information is almost more important than being able to memorize text and lectures. If you can only be taught, that you rely on schooling. If you can learn, than your limits are only based on time :)

andhof-mton The state of Linux gaming in the SteamOS era

One of linux's biggest issues is that linux hasn't been developed with consumers in mind for such a long time.

Thats why I opted to use mint for recording DevCasts: https://www.youtube.com/user/devfactor

other linux distros offer tons of tools for programmers, but are difficult to beginning users or non-programmers to migrate over to.

In order for Linux to really catch on, they need to offer at least a basic level of tools to attract regular (non-coding) consumers.

andhof-mton Side projects

I've got a side project. And chances are it will never make any real money. But I opted to do it because I know its a pain in the butt to make, and if I don't likely no one else will (or at least do a good job).

Nicely edited, free, organized CS videos. I'm opening sourcing my education: https://www.youtube.com/watch?v=4nyzl3pVXp4

andhof-mton From the startup who allegedly stole software and raised $2M with it

I worked as a contract engineer for several years and here is my take:

Typically in a contract relationship you have alot less obligations than hiring a salaried employee. At the same time, this person is using their valuable time towards your project. As a result of this, they usually ask for compensation which is agreed upon beforehand.

You agreed to a certain amount of compensation, and than chose not to pay. Sometimes contractors do not meet expectation, and I've seen this happen. But if you have already agreed upon milestones it is only appropriate to pay them at least up to the point at which you request they quit or fire them.

If you did not agree upon milestones (which a business with your funding should have.) You should still be paying him for the work done. Your disagreement over his work could cause his family to go hungry for a week. Such is the life of a contractor.

All in all, perhaps both of you performed without much regard to ethic. He did a shoddy job and you refused to pay. But your running the business and as a result have a lot more to lose from a bad image.

Just pay up and move on.