HN user

seanewest

42 karma
Posts1
Comments52
View on HN

I sincerely believe that programming has gone through a couple of paradigms over the decades. For instance it used to be a good thing to never be scared of architecting a solution from the ground up (and the best often did) whereas nowadays our ecosystem of libraries and tools are so vast that it much more often is overkill, and the architect mentality often a handicap. (This is obviously just one person's opinion)

Sounds principles are sometimes tied to these paradigms. For instance in past years one could maybe say "never use a tool that you don't know well" whereas nowadays with all of the layers of technologies that you are forced to work with it may have changed to just knowing why you have to use a technology and knowing well the aspects that you are using it for.

Also, there are by now many generations of programmers, and we might not want to admit it but the people that grew up on assembly do tend to have different sensibilities than the people that grew up on scripting languages. With these generations often come ingrained mentalities that are tied to paradigms that are tied to principles which in fact are still subject to change.

I think this shows that standards bodies could implement less native language functionality and let community-made libraries/tools compete for those areas. ES6 goes so far as to implement a native module system, seriously calling into question any effort by the community at large to implement a competing system (e.g. browserify, requirejs).

AirType 12 years ago

Would you buy an app that allows you to program on your phone (that is sensitive to the limitations of the on-screen keyboard)?

AirType 12 years ago

And then I go to shake somebodies hand/ wave to somebody / hold a sandwich and I have this thing stuck to my hand.

Edit: Might be different if it wasn't so hard, big (across my whole hand), and plasticy. Gloves and rings don't seem to cause much trouble during day to day activities.

There is a difference between research and academia. Academia in an institution, with specific ways of becoming a member (thesis, tenure) and structure to support the sharing of information (journals, conferences). These structures don't fit well with startups.

Behavioral research and drawing insights from huge amounts of social data is definitely useful for the startup industry. But people can do this completely outside of academia where there aren't massive barriers to entry. And they can share their findings using blogs, books, github, consulting, etc.

You can get to 40+ wpm pretty easily on a standard iphone. Kids these days have no trouble typing fast, one-handed, on their phone.

As for programming -- a language could be invented that is on-screen keyboard friendly (no brackets, etc).

How does this make my life better/easier? Tv's have been trying to do this and nobody really cares. Take the Nest example ... why don't I just literally turn the Nest device?

I'm not saying this couldn't have a practical use -- just that you aren't proving it.

Is TDD dead? 12 years ago

to create business logic where there already exists a generally accepted architecture.

I TDD'd for almost 3 years using Rails and this sounds pretty accurate. TDD pushes back on you a lot more when you have no clear underlying and preexisting architecture.

Ok, but I would still be creeped out by Amazon estimating details about me by using facial recognition techniques. I'm much more comfortable with them knowing about the products I choose to buy because I am aware of the information I am giving to them.

That would definitely be true if there weren't a lot of native speakers of your language in the open source community. The link I gave was (I believe) in Mandarin, and there are a lot of Mandarin speaking individuals in the open source world.

I've worked in the AAA game industry and there are many factors. When you break down the interests of companies this seems like just a product of economic self-interest, financial risk, volatility, and publisher/studio relationships.

But the truth is that the practices of industries are often based on what the employees are willing to take. Employees in the game industry will come back after being fired ... and fired again. They won't quit their job even though they work 80+ hours a week for months on end. In other industries, this would never fly, and practices that assume you can do this to employees would have never caught on, because the employees in (many) other industries won't as consistently take that abuse.

The practices of the gaming industry have, over the years, formed around this fact of nature about the employees. None of it would be this way if employees weren't willing to take the abuse in the first place.