gry

I used to run BeOS on a Umax c600x280 Mac clone (PowerMax, Umax, Motorola days). I loved it because the UI was responsive. There was no lag. It also introduced me to the command line.

The previous year, I tried an mklinux install. I couldn't tell upside from down. I didn't know enough to "man" a command, let alone which commands to man.

I'm sad Be never became OS X. I wonder what Haiku/Be would be today. Remember the first OS X version? It was slow and buggy. 10.1 was usable.

Maybe Apple would've made a slow, buggy OS B. Back then, it was on.

Why?

Oh, oh! I tried to find a book I have with the Therace-25 case study. If I recall, race conditions tripped the integer byte datatype and fired radiation at that point in time.

Ten years later, I've meant to finish the book. It's in a box somewhere.

I think the author meant learning where Django ends and Python begins. MVC is one abstract concept built on another, OOP. I can see if someone comes from a non-programming background, it's daunting, outside in.

Thank you. I've heard fantastic things about FreeBSD for a while now, and now in combination with the micro instances, I can learn and experiment. My EC2 playground is already ported over to FreeBSD, portsnap updated, extracted with a fresh nginx install.

It's been a pleasure to use thus far. Thank you, again, Colin.

CrashPlan, friends. CrashPlan.

I'm addicted.

FYI, there's a typo on the tutorial. "pefect" on the finish screen.

Have you _tried_? It's not easy. Every container has audio/video unpleasant permutations. Mike Rowe should do a show on transcoding.

We're using Zencoder daily and ran into an issue where users uploaded WMVs and the output video and audio didn't sync. It's a little known Windows Media Video Screen codec. Zencoder fixed it for us and we're paying them $100/month. Personally, I think they got the raw end. :)

Transcoding, like cryptography, is best handled by those who know what they're doing. It's dark in there.

Cache: http://webcache.googleusercontent.com/search?q=cache:http://...

Edit: also -- http://news.ycombinator.com/item?id=1889877

Bonuses are a one time commitment, while raises compound. This is a big deal.

You're right. The distribution isn't clear. It doesn't sound like a flat 10% raise. Yet, it is a 10% raise, no?

Don't confuse passion for focus. Passion pulls you. Focus pushes you. You need both.

Because this was from 2005. :) While old(ish), I had a conversation with a coworker and dug it up. Seemed relevant to HN how things work.

As an aside, holy moly.

As Michael Hartl [http://railstutorial.org/book#sec:1.1.2] said, you scale a site, not a framework.

Or language for that matter.

The details on system strategy, design and architecture are far more interesting and valuable than who is running what, other than appeasing unfounded fears.

In 1998, Apple removed the floppy drive from the iMac and extended to all their products.

In 2008, Apple removed optical drives from the MacBook Air. People concede this will extend to all their products.

The optical death will be faster than the floppy, that's for sure. I'm curious, what's next?

I currently use JIRA with Greenhopper and Bitbucket. We're currently a team of 15.

My Atlassian experience is only with JIRA as a developer. I'm with mml. The user interface drive me nuts. It gets in the way of me communicating with the team.

The dashboard reports things like time changes. "gry changed the Time Spent to '13920' on FOO-1000" I don't care how many seconds someone spent on an issue. If you have to configure a humane interface, something is wrong.

This is a small example. It takes my locus of attention away from doing what I'm paid to do, write software.

I need to communicate with the team and ask questions in order to get more information to complete an issue. I'm still responsible, yet our workflow requires us to assign the issue to someone in order for the question to be answered, then assigned back. It feels like I'm shuffling tickets rather than communicating around a ticket. The emails sent aren't humane. Don't get me going.

Yet, I can't reply to a JIRA ticket via email as a standard install?

The gist is, after using JIRA daily for seven months, I'm struggling. It feels like the user interface reflects the data model and I don't want to learn it. I get it, it's powerful. But why introduce how complex it is right away? There is no carrot. There's a carrot pile and when you're building velocity, it's not fun to jump over.

The little research I did suggests a 4-6% unemployment rate is healthy, so it seems a neutral color would be preferable.

Per your mention, red is definitely a warning affordance.

Now the places lower than 5%, I want to know why. There's something either insulating them or the coasts are the other extreme.

Also, I want to see this as the US pulls out of it. Will the coasts recover first and trickle back in? Or, will the healthy parts of the US grow outward?

This is a dark pattern.

It plays with color spectrum, pitting red against violet. Not fair. Roy G. Biv?

Now, there are some messed up things like the south -- it appears severe on state borders, thought the black line probably compounds it.

There is something very interesting and valuable here, yet it doesn't feel honest.

--

EDIT: Reviewing the color spectrum red and violet are next to each other. It felt more severe than it was. Perhaps because violet is compressed into 3 percentage points (purple, violet and dark purple), while there is red, orange, orange-yellow, yellow and cream for the "good-ish", all strong and not neutral.

Of the two public people who left Engine Yard, Ezra and Yehuda, they have different qualities. Both notable and oft overlooked in our tech-bent community.

Ezra writes technology and Yehuda informs technology.

I see Ezra doing things beyond me. I see Yehuda bridging the gap between myself and Ezra.

It doesn't matter where they are. Watch each with their strengths and you will see fantastic things.

I saw a comment here once which makes lots of sense -- find a programming exercise you find interesting and show it as an example. You a) show interest in developing your skills b) show your style and c) don't have to worry about showing something which doesn't belong to you.

Zerigo seems promising. Looking to use it on a project for myself.

http://www.zerigo.com/managed-dns

> Shure SE530s keeps everyone out of my head [snip]

When I gave up headphones, I realized how much noise I subscribed to. I found it's not the keeping everyone out of your head inasmuch as it is the general quiet with the occasional person and it feels more disarming than expected noise (something piped through buds).

In a couple short months without headphones compared to years with, I prefer the quiet with interruption to constant stimulation.

2) Upvoted.

I started three years after my first full-time gig (I was 25 at the time). I got into more trouble because I didn't say no and then had to manage the client management.

Over the last ten years, Apple produced above average products. Their growth reflects it; as does their marketing hubris.

Why lie? Why cover empty boxes? They have enough goodwill and fanboyism without having to manufacture an aura. They curate it, no doubt. Which leads me to the hand-picked reporters. Calculated, definitely.

The reporters a risk? Nah. If Gruber yanked a cloth, he'd gain notoriety, be escorted out and others would glimpse something in a relatively similar form-factor or not at all (say, the iPad a year ago).

It would suck for Apple. But can you imagine the expectation over an iPad being revealed from a PR event went wrong? The expectation would be even higher.

There is little risk. They can manage. It seems like more work for Apple to lie at this juncture.

How do you measure interference? How do you improve reception if you have a half-dozen, dozen, or hundred arbitrary radiation sources? Maybe they missed the PR move with everyone else. Color me impressed.

If Apple could kick out a product in a couple months, I'd believe it.

Subscribing to Occam's Razor: they hid real products.

They have a year or two pipeline. Google/HTC/Motorola would eat them alive. I have a hard time believing they are manufacturing a coverup to this degree within 22 days. I write software for projects a couple orders of magnitude less than Apple's taking on. There's no way they can fake this.

It's presented well. This is true.

Apple's Lala purchase has little to do with keeping Lala at bay, nor disallowing a competitor to purchase it.

Their acquisition history speaks for itself:

http://en.wikipedia.org/wiki/List_of_mergers_and_acquisition...

While Lala, Placebase and Quattro are notable because they fit in the Google space, the quantity of acquisitions suggests to me Apple is still deliberate about their purchasing -- and a defensive move is not a good enough reason.

Lala's purpose at Apple is specific and grand; it provides another something to enrich our world and their ecosystem. I have little doubt.

I've accepted email validation is like security, better left to libraries by people smarter than I am...TMail with over 2000 test cases.

But we know a valid email address when we see it, right?

--

Edit: Nicely done, HTML5.

> Real root cause: you were born.

And they were born. Seems to me root cause analysis is a fancy name for managing people. Bugs don't get upset if you fix them...

I wonder about this, same for my bank. My theory is alphanumeric plus one, maybe two symbols means there is a lower probability of some sort of SQL injection. Perhaps a greater risk for exposing one account, but lower risk for exposing many.

It's the only explanation I can come up with.

Sorry, I guess I wasn't clear -- I found the two sentences from the I quoted from amusing because the both descriptions are technical, while "in technical terms" a touch moreso, but the former doesn't strike me as layman friendly.