1,329 karma · joined July 9, 2009
Kudos for making extra time for your kids. I plan on doing the same.
http://en.wikipedia.org/wiki/Laughter_in_animals#Dogs
(I own a pretty happy dog myself but I'm not sure if I believe that dogs laugh.)
Bullshit. My first post-college job paid $550 per month. Deciding that this wasn't the best way to live my life I networked until I found a lead and then chased a CEO for two months by calling him 2-3 times a week until I got a job. And that was just the beginning, not some magical doorway into success.
> When the economy improves
That's a very dangerous assumption.
My college cost $16k per year plus living expenses. It's a long story why I was going there as opposed to a cheaper state school. My parents did pay for part of it though I had to take out $20k+ in student loans and pay for the last year or so outright.
> from poorer backgrounds
I'm from a military family, lower middle class.
> It is in no way their fault for not achieving "greateness"
I haven't personally and that really wasn't what I was suggesting.
> Furthermore, my generation (20-somethings) grew up in boom years
I was in college in the 90s, boom years. Things went to shit a year after I was out.
> we have the biggest financial crisis in the past 80 years
While the current economy might be as bad as the Great Depression by some measure, you are not living through the Great Depression.
[Edited for clarity and civility]
I'm pushing 40 and have older siblings in their 50s. Only one of them went to college right out of high school (more went later on when they could afford to pay for it) and the others joined the military to get a start in the world. All of my siblings -- minus the one under lifetime treatment for depression -- are successful today. They all have fulfilling careers and healthy families. None of them had it easy.
My parents (begrudgingly) paid for (most of) my college. There was quite of bit of resentment in my family as I had grown up assuming that I would go to college and someone would pay for it, a fairly common belief at the time, at least among my peers. After changing majors a couple of times my parents told me I was on my own. I was angry at first and then I started a small business with some friends, worked hard and finished.
After college I moved to another country and worked hard to get a career-path job. After that I worked hard starting my own company in that field. Apart from the degree my parents helped pay for I did it all on my own steam. Those decisions I made -- finishing school, moving to another country, quitting a job to start a company -- those were the ones that defined my life and paved the way for the things that I enjoy today. (I'm not suggesting I've arrived anywhere, just that I've acquired the tools to live a fulfilling life.)
Whenever I meet young people (and by young I mean just out of college) I'm sometimes very impressed though I'm often shocked at how much they expect from the world. The impressive ones seem to get it and are working hard either on their own businesses or taking the most aggressive route through graduate school somewhere interesting -- doing what it takes to carve out a niche. The ones that don't impress me think that getting a degree (or even not getting one) means they're going to have a comfortable life, free of hardship.
It's not just young people though. I see a lot of people my age who cynically pick up a paycheck every month in a field they're not passionate about, that they're not truly invested in. Then they completely fall apart because they "got downsized" and they go frantic on FB looking for a lifeline. These are the same people at different stages in life. If you're willing to dig in and make your own way then you might get what you want out of life. If not then don't be surprised when life goes sideways.
> Although Cocoa methods that indirectly return error objects in the Cocoa error domain are guaranteed to return such objects if the method indicates failure by directly returning nil or NO, you should always check that the return value is nil or NO before attempting to do anything with the NSError object.
I wish it were a little bit less cryptic. If it's guaranteed then it's guaranteed, no? Is it possible to get a non-nil error object even after a successful call? Is it possible to have the opposite happen? Makes very little sense.
[Edited]
I do like the idea of something simpler than AFNetworking though. While AFNetworking is a great library it feels a bit too complex for what it's doing at times. Depending on whether or not I need RestKit in the next project I do I might use this instead of AFNetworking.
Thanks for sharing this.
It wasn't that the candidate was negotiating, it was that the candidate showed herself to be a bad fit for the hiring college. The salary she asked for may have been "market" but probably not for a small college. The other points were mainly about limiting the amount of time she would be teaching -- which is not what a small college wants to hear.
The fact that they probably had trouble deciding between a few candidates meant it was easy to toss her out of the pile and go with candidate #2.
If I got an offer from a scrappy young startup I wouldn't counter with a list of perks someone might expect at Google and/or a bygone era.
When I say simple things I mean what's obvious for someone who programs primarily in imperative languages, like top-down, line by line execution in functions or local variables in functions. If you can take the same functions and understand them as operations on lists of things then both ways of looking at the problem are valid, though the latter won't be obvious without having the relevant experience.
> But when you see a possible fit for Haskell (I would hesitate to make 'obvious' be the bar), have you tried to persuade or demonstrate the advantages?
I have yet to. Again, I work primarily with Obj-C. Integrating Haskell would mean complicating a fairly elegant collection of tools and libraries. "Hey I like FP" isn't something I'm willing to sell to clients nor do I think it's the responsible thing to do. I go to great lengths to ensure that I'm delivering a product that could be understood by and maintained by developers with a wide range of experience / skill. Integrating a second language / paradigm into that without any clear gain would be counter to that.
> Why not find customers/areas that would be open to using Haskell?
For me it's really a chicken and egg thing. It's not easy for me to bring Haskell into my professional or even personal projects so I'm not experienced enough to go after primarily Haskell projects. What would make me consider it would be significant downtime caused by a lack of projects in the language(s) I'm already familiar with. Until that happens I'm not sure I'll make the jump.
I could possibly see writing libraries in Haskell but again it's hard for me to make that jump when I know I could write it faster in C/Obj-C because of my familiarity. What I like about Haskell (the type system, how succinct it is, functional purity) I can get most of the benefits of in Obj-C. I rarely if ever use dynamic types and I tend to write Obj-C (well, more and more these days) in a functional style by leveraging the relatively new addition of blocks.
I like Haskell. I like it in theory and I like playing around with it. I like the discipline it requires having to re-think "everyday" things in order to solve them in a new paradigm. I started with Python and then learned half a dozen other imperative languages so Haskell is utterly alien to me apart from the most basic concepts like recursion. I liken it somewhat to learning Vim -- you make the simple complicated and gain something in the process. Haskell is the number one language I wish I was working in at any given time.
So why am I not using Haskell? Most of my time is spent on OS X and iOS. While I could shoehorn Haskell into a project it doesn't make business sense to do so. I couldn't justify the extra time, complexity and I certainly couldn't justify it to a client. There simply is no good answer to "what about the next developer?" and other related questions. (I think this is why shoehorning a paradigm into an existing language is much better approach when you have a tight coupling of language and platform -- I'm thinking of RAC here.)
Give me something to work on where Haskell is the obvious choice and I'd be all over it. Until then it has to stay in the toy box.
If you said you put together a list of emails 10k in number I'd believe you, though I'd say a lot of those emails are worthless. I was a PR firm, or at least a founding partner in one, and those kinds of numbers aren't realistic if you're talking about having a valid, active contact and actually having some meaningful interaction with that journalist. PR, or at least PR done by professionals, is always quality over quantity.
The kind of PR you're talking about is what's provided by sites like prweb, which is just north of worthless unless your sole metric is the number of places that have re-printed your press release.
Most programmers here (myself included, I changed careers) would, I imagine, cringe if the marketing guy said he was going to do some of the coding. There's a reason programming is a profession and people who know what they're doing get paid well. Same goes for PR. You probably can build that iPhone app yourself, but you probably shouldn't. Leave PR to the people who do it for a living.
Having said that, most small companies shouldn't bother with PR. Small companies should focus on sales. I say this from experience having built companies and having done PR for companies from the largest (major airlines, telecom companies, hotel chains) to the smallest local businesses. Put another way, when we launched our PR agency we didn't PR ourselves -- well once, and it was a complete waste of time.
A mention somewhere might be neat but it's nearly worthless for a new company. If you don't believe me dig up the research on how valuable that mention in TC actually is.
When journalists start coming to you, hire a PR person.
I live in Thailand where most toilets have a handheld sprayer next to them -- part bidet and part firehose. Awkward at first but it's hard to tolerate a paper-only cleansing after you get used to them. While European-style bidets have their charm the furthest expression of this luxury is the Japanese toilet. Push button controlled, temperature regulated and with a drying cycle that's like a spring breeze on your privates. After using one it's hard to understand why they're not the norm.
We almost found out. As insane as that plan was, it was relatively sane compared to this, and similar, tests:
I think I was on the $20/month plan. My overall impression of Dropbox was that it was always there when I didn't need it / never really there when I wanted it.
1. Most of the stuff I need to share with myself or others lives in Github.
2. When I want something to sync with my laptop (usually when I'm running out of the house) it's often behind of bunch of other files and means it will have to sync over a mobile connection if I'm going to get it. This usually means using a thumb drive rather than deal with syncing.
3. And this is entirely my fault: I had a handful of older projects in my Dropbox folder that weren't mirrored on Github or anywhere else. When it came time to actually dig one out it turned out that Dropbox had had some manner of sync issue and had renamed dozens of files in my .git folder. It was unusable.
I dropped down to the free plan and uninstalled Dropbox from my laptop. Haven't missed it at all.
The point I was making is that talking or being in front of a group of people aren't terrifying by themselves. You're likely to be worried about being judged in some unfavorable way. Don't be. Shit happens. Just get through it -- without drugs or Jedi mind tricks -- and you're realize it wasn't that big of a deal. Do it a few times and you'll be a natural.
It's valuable to realize why you are nervous.
If you were asked to get up in front of 200 people and stand there silently for 10 minutes you wouldn't think twice about it. You're nervous because you're trying to accomplish something: secure investment, win new business, impress people, etc. You're nervous because feedback is (often) immediate and you can be challenged directly. You're nervous because you're not completely comfortable with the subject matter.
You can deal with those things. Learn to (intelligently) say "I don't know but I'll get back to you". Learn to deal with rejection. Learn to not take yourself so seriously and make a joke if you screw up.
No it doesn't. All speaker drivers act as bandpass filters. On the ends of their frequency ranges those +/-3dB points are generally their -3dB points. For most speaker drivers their low frequency cutoff will be caused by the resonance of their motor, dropping off rapidly after that point. The upper frequency limit will be caused by the inductance of their motor's coil with a similar drop off above it.
It's unlikely that the iPhone speaker could reach 48kHz. If you look at expensive high frequency units (tweeters) they'll generally top out at 20-30k. A lot of headphone drivers (which are more similar to what's in the iPhone) barely make it to 20k.
> You can still make some noise higher or lower than that, it will just be more distorted.
Again, nothing about distortion here. A speaker driver will output sound outside of its -3dB points, but, obviously it's going to be much quieter (-3dB is already half as quiet).
For me it didn't extend beyond that however.
As I understand it the former was created before the meteor bundle command was available.
1. Bangkok is not cheap. If you want to have a life that resembles anything you're used to coming from a Western country, you're going to live in Bangkok and you're going to live in a relatively expensive part of the city.
Yes, you can live in a concrete block with plastic furniture and eat noodles on the street every day. You can probably get by for not much more than $1k doing so. When you can no longer stomach that, you'll find the city is quite expensive.
A decent apartment in a favorable part of town will cost you $1300 - $2000 per month. I don't mean a family-sized place, I mean a 1 bedroom with a "livable" amount of room and furniture that doesn't give you the willies.
Once you're sick of your local noodle vendor you'll find food prices quite high as well. My wife and I spend more on groceries than we did when we lived in SF (we shopped at the Safeway in the financial district). As for restaurants: We grabbed two meals outside yesterday. One was dim sum that came to about $30 for the two of us. The other was a tonkatsu place and the bill came to about $25. While that's probably cheaper than the US (for the same quality) that's hardly a meal for $1. We spend over $100 for a meal often. I don't know anyone (Thai or foreign) that would consider that overly expensive.
Wine and imported beer are expensive and the taxes are going up. American craft beer is going to go up to $10/bottle direct from the distributor. If you can stomach the local swill (think Budweiser without the quality control) knock yourself out.
When you're sick of taking taxis and the BTS/MRT, have fun buying a car at 50% - 300% above US prices.
2. Visas are not easy. If you really want to fake it here it means constantly traveling in and out of the country. The problem with that (beyond the fact that it usually means traveling to the least interesting parts of the surrounding countries) is that they limit it to a certain number of tourist visas for every six month period or something similar (I can't remember the actual rules, sorry).
The common way around this is to use a "visa service" which basically means you're paying someone to bribe someone to look the other way. It's not only illegal, the rules for it change seemingly month to month, based on whoever ends up in a position of power in what embassy.
To do it properly: a) register a business with the requisite capital and Thai shareholders, b) get the appropriate visa c) get a work permit. I've been through it. It's not cheap or easy.
To not do it properly means breaking the law in a country where you most likely don't speak the language. Have fun with that.
3. Sex isn't everywhere. My wife and I go out for drinks 1.5 times a month and I can't remember the last time I saw a prostitute. If you're going somewhere with a free flow of hookers then you're probably seeking that out. I see young people do this quite often -- the only difference between these young people and so-called "sexpats" is that young people often go "ironically". They're all equally as stupid.
4. The local talent pool is mixed. The entrepreneurs here are generally managers, not doers, so you're probably never going to find a technical co-founder. Programming/technical ability on the whole is quite low. Try browsing the website of any publicly traded Thai company and you'll see what I mean. It is possible to find good graphic designers, administrative types, etc. Salaries are low here so that could possibly be an advantage. Having said that, I know people who have built large tech companies (100+ employees) and the consensus is that the disadvantages here outweigh the advantages. Most people I know in tech here outsource to Eastern Europe or somewhere else.
Investors are hard to find and mostly unsophisticated in relation to tech. Tech-savvy ones do exist, but they generally buy companies outright and keep you on as a glorified project manager.
5. When you're ready to put down roots, you'll find doing things legally is an expensive pain in the ass and -- here's the kicker -- you'll have to give up 51% of your company to one or more Thai people. If it's not someone you've known for a decade then, well, good luck with that. Yes, there are ways around this but they require you to put your company in a legal gray area.
6. Inflation isn't rampant. Cost of living has gone up considerably on the scale of decades but it's pretty hard to notice in a few months.