HN user

collint

358 karma

@collintmiller https://github.com/collin collintmiller@gmail.com

Posts10
Comments127
View on HN

Hello Alan,

I'm curious if you've read much about Activity Theory. (in particular, Yrjö Engeström's Learning by Expanding.) I feel like it's compatible with much of what I've heard you discuss in lectures. Is it something you have an opinion on?

Irrelevant how?

Is it irrelevant that the examples fail to back up the assertion because Peter Thiel is the one making it?

The 'big idea' expressed in this blurb is that it's 'easier to copy a model than to make something new.'

And the supporting arguments show off the opposite case just to associate the book with becoming the next industry defining billionaire.

Whoever wrote this blurb is either not thinking clearly, or is banking on readers to not think clearly.

There are much better example cases for that argument, but they aren't as flashy.

Because it's not like marbles. It's not a math thing.

It's more like a canary in the coal mine. If the canary dies, you should check on the air quality. If they went through the trouble of removing the brown m&ms you have a fairly strong indicator they actually read the document in the first place. And a strong indicator they have a good attention to detail.

Wisdom is knowing which approach to take.

Intelligence is being able to apply the given approach.

edit: Unless the approach is 'hit the other one in the face', then all the intellectual posturing in the world won't do you much good.

Money is influence, the source of that money is influential.

What are the perils of the other sources of money in open source?

For quite a long time the best documentation and guide for using Rails was a book.

Quite a few of the top contributors to Rails have published books about it.

Documentation is very much a weak point for open source. Should we criticize those who contribute to open source and request money for the documentation?

If not, why spread FUD around the idea of asking for direct monetary support of the code itself?

After Skeuomorphism 13 years ago

Can't speak precisely to the application used in this example, but a common and important feature of programs like this is mapping the knobs and sliders of the UI to real-life knobs and sliders on a physical control station.

Some consoles even have servos so the binding can go both ways.

Would anybody be seriously interested in this? I'm currently writing code for a printshop that does fine-art reproductions of various size on paper, canvas, and stretched canvas.

We're somewhat under our print capacity and I could easily justify the time building an API on next to our shopping cart and fulfillment backend if anybody has genuine demand for on-demand high quality prints and reproductions.

Shoot me a message: collintmiller@gmail.com if you'd use the api.

I'm only using ST2 because TM2 took forever to release and even the the alpha wasn't compelling.

So I'm much more worried about developer fatigue than bloat in my editor choice.

yeah, it's not directly attacking your 'inactive' memory. Just the disk cache, which shows up in the chart as 'inactive'. I'm not familiar with other cases that fit into the 'inactive' piece of the pie.

I have regularly seen 1-3G of ram get free'd up on a 'purge'

A good way to stop being a "nobody" is to get your names on your online properties. Twitter handles on your blog posts would be a good thing.

It took way too much effort to track you guys down on angel.co, and even then I don't have twitter handles.

( ps: I'm also hanging out in Iowa, hacking on a startup. Hit me up @collintmiller, maybe we can cook up some ways to remind people this is the state that brought you the computer. )

Gmail Tap 14 years ago

I'm not sure if the joke is Morse code on a phone, or using two buttons for Morse code.

How exactly do you expect build any automated tooling around your ecosystem of raw socket applications?

For example: indexing

You're going to need something that solves the problems HATEOAS solves when it comes to multi-service coordination.