HNHacker News
TopNewBestAskShowJobs

tristan_juricek

147 karma · joined December 7, 2008

submissionscomments
tristan_juricek··on Startup = Growth
This article might just be my point of reference whenever I get a bit too much "valley hate". Like, when I start reading a bunch of the ideas coming out of the blog from 37 Signals.

I still think that for every serious genius, there are a lot of copycats. These copycats create this gigantic echo chamber of ideas. It's a ton of noise from a lot of likely failures. That noise can feel dishonest.

After reading this essay, I'm left with a sense that startup land is probably the best, dare I say more honest way, of turning investment money into new technology and jobs.

I'm actually left wondering about the relationship between "normal small businesses" and bankers. It feels adversarial in comparison.

tristan_juricek··on What killed the Linux desktop
I would think so, but OS X has had several great or important applications within it's ecosystem, that break UI conventions.

Twitter clients used to be a playground for new UI concepts, none of which came from Apple. The Sparrow mail client was a good example of something probably more influenced by Tweetie than anything else.

Even Apple doesn't have a ton of consistency. iTunes continues to baffle me with random changes things like what resize does. The App Store app shifted the window management buttons.

So I don't buy that the OS X ecosystem is a "cathedral" at all, just a bazaar with better taste.

What's interesting is that I noticed the standards of design for Mac apps were significantly better than Windows apps when I "made the switch" several years ago; and these are for apps that were not coming out of Apple. I could never entirely figure out why; the ecosystem was just more attuned to details.

I posit that Apple was helped by having the right people excited long enough to get a great ecosystem going.

Linux didn't die because it's a bazaar; every modern app ecosystem (OS X, iOS, Android, the web) functions like a bazaar. Linux just made it absolutely painful to set up shop.

tristan_juricek··on Rendering Views in Backbone.js isn't Always Simple
Yep, I was wondering why "render" would need to be called multiple times.

I usually start off by doing that because I'm lazy, then something usually bites me in the ass (usually - oh hey, we need a transition effect).

And the end result is a bunch of "sub rendering" methods that get called in render ... and as callbacks from model change events. (It's awfully nice when you have to load everything off the server - no default state in the DOM.)

tristan_juricek··on Ouya Breaks Kickstarter Records
Doesn't it seem like a group might be able to use Kickstarter to "speedup" the something like the process Github used to get to it's Series A? You know, start a generally profitable business and then work with a very knowledgable investor to take on a huge piece of pie?

Just seems like a VC might even prefer a group that knows what it wants and how to get things done. They might be more ready to disrupt. And they might have a great culture with the right priorities.

I wonder if we'll ever see "Pixar in reverse". A company that can deliver an entertainment product turn into some kind of revolutionary hardware product manufacturer.

tristan_juricek··on Why We Don't Believe in Science
A scientific idea is typically something that can be proved incorrect. :)

(This would be opposed to a lot of religious beliefs, where you either have faith, or don't. You can't really prove God doesn't exist.)

I'm not sure where philosophy lies. Somewhere between the two, it seems.

tristan_juricek··on Software Raises Bar for Hiring
This just smacks of big dumb companies trying to "automate away" HR and not really paying attention to the consequences. And, candidates not figuring out HR systems.

What I fear, however, is that this isn't really a problem for the executives for a public company. Their real compensation these days is all tied to stock prices; I don't see the incentive to really care about HR. How does adding people change the stock price? (Usually I only hear about it from the other way; cutting jobs to cut costs.)

Have you ever heard of investor pressure to hire candidates?

tristan_juricek··on Customize Gmail's Buttons: Replace Icons With Text
Why not allow icons and text (a la nearly ever Mac toolbar I've used)? That would seem, to me, the easiest way to "skim" a toolbar.

Icons can be smaller (like the document editor toolbar), but it doesn't seem like Gmail's really pushing the size limit.

tristan_juricek··on Single Page Web Apps with Backbone.js
We ended up doing something similar here with multiple views. Similar, but different. Our app is very desktop like, with basically a layout container with sub-parts that re-render. Instead of a "widget" system, I created a parent-child hierarchy, where parents would bubble child events on up. This way, the router just receives app notifications from a 3rd or 4th level child and can decide to "switch" the main view. The parents cleaned up the kids.

It worked for this app, but I don't think our pattern was particularly useful unless you had to build the kind of complex "pseudo-multiframe" kind of app we were building.

This is why I love the approach of backbone. It's easy to read, and establish new patterns. Our "multiple view" pattern we're using is a little different from what sendhub is doing, but I think it was fairly direct for both of us to get what we want.

tristan_juricek··on The Linux Setup, Noah Lorang, 37signals
The fact he rarely uses a notebook fits my own experience. How many developers actually develop out in cafes, or do so many presentations that you'd need a mobile computer? Probably better to customize a workstation like this then sweat about mobility. (For that, we have phones.)
tristan_juricek··on Teacher effectiveness ratings, programmers, and Khan Academy's data
I don't see a problem with effective metrics; they might help identify where teachers might need help.

The problem, is that usually nobody really does proper statistical analysis. The metrics I've seen, are usually like "mean student grade performance". In which case, what you'd want to do is have a really small class of smart kids. (Ergo, kudos to the teacher who finds a way to dump the idiots.)

I do think, however, you could do polling of teachers by asking the students, teachers, and other staff. In most cases you could easily have enough coworkers to figure out who's respected and who needs help.

tristan_juricek··on How Apple's Top Secret Product Development Process Works
I see two major problems being solved here:

1. "too many cooks in the kitchen" design-by-committee crap

2. "sunk cost" pressures to deliver on investments

What's interesting is how few people are involved in making decisions, given the size of the company.

As an engineer, I wonder if I would feel more or less significance over my own decisions, given the constant executive feedback, and what the relationships with "the EPM/GSM mafia" feels like. My sense is that it's probably fine, given the talent level of the design group.

I also wonder how many of these startups have been killed. I have to think that keeping things secret means that the execs can halt projects without reporting this to investors.

tristan_juricek··on "DevOps is ruining my craft"
Ideally, this is true.

But, I've worked in places that had bad resource planning, and didn't allocate the same kinds of resources in staging. When we had performance problems, there was no place else to go.

It can be hard to convince people to take their expensive hardware and IT time to set that production system up, and now, "duplicate it so we can debug". Eventually, I think you just give up and go somewhere else.

tristan_juricek··on Lessons from Moneyball
If you haven't read "Thinking, Fast and Slow" it really summarizes the problems in a lot of decision making in a very clear way.

I'm still reading through, but, you have two major actors in your brain. A "fast" side, and a "slow" side. The fast side makes gut decisions, and the slow side, well, applies more complex judgements and can include a more unbiased view of the world. There's a ton to this process, but importantly, the fast side is very happy to jump to conclusions when presented with missing information.

The lesson of Moneyball, then, was that the "fast side" thinking clouded judgements of baseball prospects by filling out ridiculous statements like "he's got a hot girlfriend, must be able to have the confidence we need on the field".

I'm not sure how you can use the baseball metaphor in terms of software design, though.

But, you could easily say that we're presented with an incomplete amount of information when building software. (What's going to happen when it runs? Who knows! Just build a nice API and continue.) So we definitely all probably have a lot of "quick learning" techniques and processes we just adopt to. For example, Googling before you just stop and think. Or using the UI techniques of other applications, because "that's how the big profit-making companies do it".

tristan_juricek··on How U.S. Lost Out on iPhone Work
> Many more people work for Apple’s contractors: an additional 700,000 people engineer, build and assemble iPads, iPhones and Apple’s other products.

I wonder, if Apple attempted to work most of those jobs in a western system, how many total jobs would there be? I'd have to think less.

As bad as this may seem, I see this sort of globalization as a good thing, because the total overall number of jobs is probably higher. (A job, meaning a steady paycheck, and not rural poverty.)

I might have read this too recently, which might be clouding my judgement: http://gmj.gallup.com/content/149144/coming-jobs-war.aspx

In the end, more jobs = fewer serious problems. I'd have to think, though, that you'd need to take care that you don't lose job counts. Western countries probably need to worry about that a bit more. I don't see how it can be done without more education and training.

tristan_juricek··on Getting Steve Jobs Wrong
Since every software company has this process, why does Apple stand out?

That's the question I think Gruber wants answered, and where this huge Bio of Jobs, probably our best opportunity to find out, has fallen short.

I would take a guess that if someone were to really publish the "secret sauce" you might find it less like a recipe - i.e., "do this and you will win" - and more like a history of a company that found smart, productive people, made them focus, and then got the fk out of the way.

I'm not sure a Biography would illuminate this. But I think Gruber's right in that Jobs probably wasn't a "tweaker" in the sense of someone actually making a tech decision. He probably tweaked people.

tristan_juricek··on Why Daylight Saving Time Should Be Abolished
Oh man I had so many stupid problems caused by developers who made two decisions:

1. "hey let's store times in the local time zone in the DB" 2. "oh the user wants their local time, I'll just use an offset"

This comment just brought back the memories...

And no, I'm no longer at that company.

tristan_juricek··on Ask HN: I think My code isn't Good enough
I've been trying practice better, as I think we all tend to mostly learn by using or reading documentation.

I started "exercising" a bit before I kick into coding. A few different exercises I made so far:

1. API Memorization: go through an API and try to build something that executes each function once. This is great with a REPL.

2. Reading code: find a sweet, highly regarded open source library, and, well, just pick up a file and read it.

3. Improving tool usage: improve typing speed, memorizing functionality of your editor, etc.

I try to do one exercise for about 30-45 minutes daily (if possible). I write down what I read or memorized in a spreadsheet. Maybe I'm anal.

I see exercises like how sports folk practice, or how musicians (I play the saxophone) do scales, etc. It just kind of rounds ya out a bit. Over time, you just get a little faster.

tristan_juricek··on Java.next() - JRuby: The Rubyists Strike Back
One of my first questions was where is JRuby is in use, and I figured linking to the JRuby success story page was in order:

https://github.com/jruby/jruby/wiki/SuccessStories http://stackoverflow.com/questions/615825/is-jruby-ready-for...

I remember someone mentioning that a major benefit of using JRuby was the stable DB driver implementations. Just don't remember where that comment came from.

tristan_juricek··on More thoughts on switching back to Java from Scala
That's not entirely fair; he's been consistently critical of Scala, but seems to like Fantom.

While he may have added that note at the bottom of this article, I swear I've read that opinion of his more than once.

tristan_juricek··on Literate Programming (and why Docco isn't enough)
I've messed around with my own literate programming system that was a more "true" system (where you have a kind of macro-like approach), and I have to agree: the docco approach is missing the key bonus: organizing your code into chapters and paragraphs and then statements.

Think of it this way, if you're building an API, you should consider usage. So you then generate examples. But not just one, maybe 3-5 of them to really do it right.

Then, as you proceed, you implement and build tests, probably down towards the end of "the chapter".

It's a different way of thinking about how your code is consumed. The "documentation systems" of the past (e.g., javaDoc) really are reference documentation on details of a method. But if you want to really grasp the system, you probably lead with examples. Maybe a picture. And you probably don't need to have to navigate to 7 different implementations of your interface Foo to figure out what the design is.

But having those 7 different implementation files is nice when you know the system later.

Where literate programming systems completely break down is the toolset. You typically can't work in "example down" mode and "single source file" mode at the same time - like, to debug, or make a small change. I've tried to build "diff and patch" between the source and the literate documentation, and when that's buggy, whew, that sucks.

tristan_juricek··on Build apps not businesses.
Yep. And "releasing" something worth a damn typically means making sure it's documented properly, hosted somewhere nicely, etc.

Plus there's that other part where the first two times I implement something it looks like utter trash, and then the third, hey, that's alright.

tristan_juricek··on Build apps not businesses.
How many projects are only a couple of hours in length? I started down this road, and ended up with a list of "learning experiences"; nothing that I'd inflict upon anyone else.

I guess I'd add "... but don't release it". If it's just to build up a portfolio, you can usually make the source code available and maybe a demo.

I do like the idea of "programmer portfolios", however.

tristan_juricek··on PG on Java - comments from 2001
I'll note that he heavily referenced a paper, "Strategy as an Ecology"

http://williamkuo.bokee.com/inc/HBR-Strategy_as_Ecology.pdf

This is probably a better reference point.

tristan_juricek··on PG on Java - comments from 2001
At, OSCON, the Eclipse "ecosystem guy" (I think it was Donald Smith) had a nice overview of what he was up to, and how he measured "ecosystem strength". It gave me pause, because that was the first thing that really nailed why tech like Java takes off. Productivity, robustness, and niche creation.

http://www.oscon.com/oscon2010/public/schedule/detail/13307

I figured I'd just drop a link to it, because it's interesting to compare with "hacker instinct". Java got the ecosystem rolling really quickly; it would be interesting to compare that kind of growth across different tech.

tristan_juricek··on Why the San Francisco Fire Dept manufactures their own wooden ladders (video)
I don't think it's just a quality concern. The video mentions a 15-year "maturation period" for the wood to acclimate to the humidity in San Francisco. If that's a requirement, I doubt there's much of a market (and space) for manufacturing to take place out in the city itself.

Maybe wood used for wine barrels? Doesn't seem like much of a market.

tristan_juricek··on Silicon Valley's Dark Secret: It's all about Age
Most programmers definition of "highly skilled" is more like "proficient with a language", or framework, etc. A lot of people I know aim for "can use stuff" rather than "master this thing", which is mostly because, hey, it's technology, and there's always a new thing.

But there are skills past simply becoming proficient in new tools. You could "master the tool", like knowing the details of the JVM memory model, and very importantly, be capable of identifying very hard problems that you can solve that those "young guns" can't.

It is incredibly rare for me to find an experienced programmer that can sell anything but their past "obsolete proficiencies" to me. Most of them sell me on the fact that they've simply been good with X+Y number of tools, where Y of them are now no longer relevant. But they never focused on developing deeper skills that might have relevance (big data problems, etc).

It's the constant shift of tools that adds a lot of this tension. Yes, we need to be able to pick up new ones (languages, frameworks, etc) quickly, but if broad proficiency is how we define mastery, this has little relevance to businesses.

I'm not saying this is easy. How do you unambiguously describe a programmer's skillset past the languages and frameworks they say they know, especially in a way that might be "future-proof"? ("I optimized my system to display 30 frames a second!" "Wow, my phone does that now...") Ultimately, if we can't clearly describe why people's experience is better, it will be hard to justify paying them more, once you become proficient with that particular toolset. Thus, I don't sense real age discrimination as much as a simple inability to sell the value of our experience.

Of course, some programmers are WAY more valuable than others, so this is a problem that isn't just about age and experience. Hiring practices sure haven't matured at all during my 10 years on the job. But, until the finance guy can see why a guy with 25 years of experience but with 3 years with tool X is more valuable than the guy with only 5 years of experience but all 5 with tool X, well, you're not gonna see the money flow.

tristan_juricek··on Silicon Valley's Dark Secret: It's all about Age
So, we should be taking care of our own career growth? Shocker.

Yes, there will be a point where your salary will not grow. But that salary is usually higher than most other skilled professions. (Note: this is an assumption; if I'm wrong, that would be interesting.)

My experience has seen very little "mastery" in programming; after about 5 years, most engineers hit about the same level of ability. (Note, I'm not saying you can't hit mastery of a particular thing, but that most don't do it.) Thus, there are only two kinds of programmers, skilled, and learning. If you don't gain differentiating skills after those extra years, why should you be paid for it?

Maybe this is the real "dark secret": most programmers don't know how to gain mastery of something useful to a business. Maybe this is what "we" should be worrying about, rather than hiring practices?

tristan_juricek··on Kindle vs. iPad Displays: Up close and personal
> with the iPad I find that I'll be too easily tempted to press Home and mess around ...

Yes, how many times have I earmarked papers only to find myself web surfing or playing games? gah...

tristan_juricek··on There is no such thing as good hiring, only good firing
A third seems like an awfully high ratio; as someone else has pointed out, there are real (and immediate) repercussions from firing.

I've fired someone before, and I'd do it again. But it was a horrible experience; and I would want to avoid that kind of experience, especially for 3-6 months.

One thing that gave me a lot of confidence was to set up a peer review system. Once I saw that the group had the same instincts I had, it was a no brainer. (Peer reviews are so much more interesting on many levels, actually. I don't know why this never occurred to any of my bosses.)

Other than this, the "one week trial period" proposed in Rework (http://37signals.com/rework/) seems like a good way to avoid a "several month realization of uh-oh". Has anyone ever tried this out?

tristan_juricek··on San Diego HN meetup is tonight 7:30pm-9:30pm Broadway Coffee in Kearny Mesa
I'm possibly interested in a Scala users group.

(Translation: I'm thinking of moving back to SD, we'll see in a couple of weeks.)

I guess that means count me in as a "maybe", which might be good enough to kick things off.

← PreviousPage 2 of 3Next →