pm

Okay.

Time does not equate to quality. Credentials do not equate to mastery. If shit's not working out for you, you're either ahead of your time or it's a shitty idea. Either way, the only person in control of your life is yourself.

Airbnb might be a bit presumptuous.

If you're going to downvote this, at least respond. I was asking a genuine question.

Fair enough, but it's not a US-centric thing (which is the bulk of YC companies), so I highly doubt that "fired a synapse" for the founders when they came up with the name.

When the Pakistan cricket team tours down here in Australia, they're colloquially referred to as "the Pakis", but that's because we colloquialise EVERYTHING, and has nothing to do with slurring anybody.

Paki, an ethnic slur? I would've thought it was short for Pakistani.

Cross-platform work is pain enough without making it torture with Xamarin.

How much of a generation getting fat is attributable to institutionalised science versus people divesting responsibility for what and how much they eat and exercise?

Yeah, I haven't seen anyone do a darkside other than him yet.

Have you actually tried writing CoffeeScript? I can't tell from your post, but if you haven't, you should really give it a go first and see how you progress. It might not be as big an issue as you think.

This is what happens when one person stops communicating to another due to lack of awareness; the other assumes the worst, and stops reciprocating. They are the only one who knows what's going on, yet it almost always comes down to them saying "Why should I be the first to re-establish communication?". You should do it because you're an adult, and the other person isn't a mind-reader; if you don't, you don't deserve any sympathy when the shit hits the fan.

Create vitamins, not painkillers? I'm not sure I would call that a great piece of advice. I've found entrepreneurs have a knack for one or the other, but I'd err on the side of painkiller if I couldn't pick either one.

What city are you in? Sounds like Hobart.

I'm still reeling at the fact the pricing incident is the only thing that sticks in developers' minds, given how easy it was to mitigate.

Seeing as I can't reply to the comment in question... the price hike article you mention is in 2011. The price hike was a change of system, and everything went up because most people were using Python 2.5 which had no threading support. Python 2.7 had proper threading support, and unsurprisingly when that was enabled, everyone's cost dropped by three-quarters. Google dropped support for 2.5 two years ago.

If were really worried about costs, you'd convert your App Engine app to Go.

It really doesn't.

Really? That was in 2011. It's now 2015.

Get your health right first. Your side project will always be there, the time you spend with your daughter will not.

That sounds plausible, though I thought any power running through it would've caused it to burn out. I was actually going to do a full disassembly with a mate of mine who was an EE, but never got round to it. We attempted to do it with my iPhone (which was dunked into a toilet in an unrelated incident), but even cleaning everything with isopropyl alcohol it wouldn't work. I didn't hold high hopes for the MacBook.

And no, water damage wasn't covered by warranty, but it was out of warranty anyhow. I just didn't want to pay another $2K for a MacBook Air (maxed out specs at the time).

How about attempting to fix the issue instead of confirming what I already knew and telling me to buy a new computer? That's what technicians are supposed to do.

Heh. I caught in the rain with my MacBook Air, and it worked fine for a day, but then wouldn't boot up at all and wouldn't hold charge. Three weeks later and rice and all that jazz and nothing. A couple months later, the charger showed a light, but it wouldn't boot and never lit up green.

Six months from the first incident, and I randomly plugged it in and it booted instantly - I was ecstatic. It lasted two weeks before it wouldn't boot up again. A week later, it booted up again, and has been fine ever since.

Beats me man. Apple "Geniuses" wouldn't touch it and wanted me to buy a new one.

My old housemate had a bad habit of getting stoned and ordering random cheap shit from China on eBay (and forgetting about it until it arrived 3 weeks later). One day he beckoned me into his room, and showed me the training kit he wanted to get for his cat. The cat was the type that keeps meowing at whoever's nearest at high volume until it gets what it wants (which usually ended up being me), not to mention had specifically come into my room and pissed on stuff while I was sleeping, so I was already severely pissed off with this animal.

I told him in no uncertain terms that training the cat to do its business in the toilet was crossing the line. The possibility of having to wait for the fucking cat to take a dump before I could go doubled with the fact I'd have to flush for the dumb fucker would be the final nail in the coffin of my dignity. I would not become the pet.

I can understand the convenience training a cat to do this, but there are some luxuries that should be the privy of humans, and sitting down to take a steamer without having to dig a hole should be one of them.

Outback public schools are lucky if they're equipped with more than one toilet.

There are many good tutorials on the Internet for a lot of things, but many make assumptions for things that aren't specifically code-related (libraries, linking, etc) that can be frustrating when you're starting. Consider it a rite of passage.

If you have any questions on anything (there's no such thing as a dumb question), again feel free to e-mail.

The purpose of an analogy is to educate a concept using an approximation of another concept the person will understand. If the person in charge of risk management doesn't understand how risk accumulates in a codebase, they're far more likely to understand the model of technical debt than options calling.

Technical debt is an elegant analogy. However, I find the majority of systems on which I work are not loosely coupled. And yet, judging from the notes left by my antecedents, "loosely coupled" was the ideal for which they were striving. Is there a metric, or at least a heuristic, that can be applied in this situation?

What you're talking about is a bad implementation of a design stemming from its inherited technology. Essentially, attempting to refactor the technology or the design first is a bad idea - fix the implementation.

I couldn't imagine they'd want to do that after all this time.

It would just be easier to reclassify NZ as Australian territory.

I relate somewhat to poster's situation, as one of my half-brothers had a somewhat related experience in rural NT, sans the happy ending. If the poster is reading HN, I'd be happy to catch you up on the state of Australian tech. My e-mail is in my profile.

I would think that by "mundane" Franklin means "not that interesting".

I used Fossil for a while, and I liked it a lot. But after using it with my team, and having to host it internally (something I didn't have the time to do properly being a startup), and programmers complaining about the conflict resolution process, we moved our projects over to git/GitHub. Honestly, I haven't looked back, even though I much preferred Fossil's simplicity.