nborgo

I don't think that's all too uncommon for native English speakers. While pairing, I pretty regularly refer to chunks of code as "this guy" or "that guy".

Maybe they picked it up from someone while learning English and it stuck with them.

Chicago, IL | Software Engineer / Team Lead | ParkWhiz | https://www.parkwhiz.com/ | Full-Time | On Site

ParkWhiz is looking for experienced software engineers to help lead development efforts on the parking platform of the future. You'll get challenging problems to work on - complex pricing models, GIS/geospatial data, transaction processing, mobile apps - and flexibility to choose the best tools for the job.

We're looking for people with:

* 5+ years of experience and the wisdom that comes with it

* Strong working knowledge of Ruby, Rails, SQL, and web development in general. You are an expert in at least one language, and have experience in more. You have no problem jumping into a new toolchain or stack

* Master of backend development, but proficient across the stack

* Ability and desire to mentor other developers, as well as continually learn and grow yourself

* Workhorse capabilities. You can keep (and ideally set) the pace with incredibly talented developers This position will be 100% development from the start, but as we continue to hire, we will look to you to help take on additional leadership roles. You will most often use Ruby, but we also have a fair amount of Go, PHP, and all the usual tools that come with the job (AWS, Postgres, Redis, Javascript, Coffeescript, etc).

If you have any questions please feel free to email mark@parkwhiz.com to learn if this position is the right fit for you.

Benefits that ParkWhiz offers:

* Competitive salaries

* Medical, dental, and life insurance

* Flexible schedules

* Paid holidays and generous vacation

* Workstation of your choice

* Casual office with stocked kitchen and a ping pong table

* You'll be working alongside a team of phenomenal people

Alex wrote about the topic after losing that sponsorship:

http://www.nytimes.com/2014/11/20/opinion/the-calculus-of-cl...

It's a nice, quick read. Especially if you're even vaguely interested in climbing.

For those put off by the first 40 lines, here's the good part:

"SonyPictures.com was owned by a very simple SQL injection, one of the most primitive and common vulnerabilities, as we should all know by now. From a single injection, we accessed EVERYTHING. Why do you put such faith in a company that allows itself to become open to these simple attacks?

"What's worse is that every bit of data we took wasn't encrypted. Sony stored over 1,000,000 passwords of its customers in plaintext, which means it's just a matter of taking it. This is disgraceful and insecure: they were asking for it.

Just as important: if I am already most certainly aware, why are you wasting my time by telling me?

The same goes for people who write "obviously". If it's obvious, why write it? If the person doesn't already know, then you sound pretentious or the person feels like they missed out on something. It's pretty much lose-lose.

On a more related note, I'll probably check this out sometime. The dashboard looks nice.

Hopefully this doesn't come off as too harsh, but would anyone mind telling me why Hype is better than Flash? Judging from their gallery, it's just as bad. It only "fixes" the CPU hogging part of Flash (and, presumably, Flash's lack of mobile support).

It still takes a long time for the initial page to load. We don't even get a loading bar, just a blank page and "Built with Hype" for seven seconds. When it does load, we still have to sit through all the pieces of the page sliding into place. The demos look like Flash pages straight from the 90s. And I dare suggest that Flash sites could be more SEO friendly.

Hype seems like all the annoyances of Flash under a different name. It seems to encourage bad, flashy design just as Flash did, which makes me wonder about your "[t]his is a very designer-friendly process" quote.

Be sure to test the "Try for free" button in magenta, too. It'll really pop with complimentary colors, which could be a good or bad thing.

Kind of. They're cut down from carrots that are made to grow as long, thin and quickly as possibly. Not exactly from a carrot that you'd find in your garden. That's not to mention the peeling and washing they go through, which I can't imagine it not changing the taste.

If your point is that "baby carrots" taste like regular carrots, then I have my doubts that you've ever tasted a good carrot.

The swipe and onion skin are pretty simple. Both of them put the images in the same place. When you swipe, the width of the top image changes. For the onion skin, the opacity changes.

Difference has some canvas magic going on.

If everyone starts aiming for the little blue center, I wonder if people have a better chance of clicking the icon. Maybe they thought of it like extra padding around navigation links. When we aim for the original icon and miss by a couple pixels, nothing happens. If we are drawn to aiming for the little blue circle and miss by a couple pixels, Chrome still opens.

Here's a more design oriented discussion: http://www.underconsideration.com/brandnew/archives/chrome_l...

I, for one, just switched to the Dev channel for the updated icon.

Moving the left and right arrows with the cursor is a great idea, especially since they don't move until you get close. It might be nicer if they would animate to the position when you first move the cursor over, though. It's kind of jumpy as is.

That pattern just might catch on.

"An earlier draft of this post said 'lucky.' I have since reworded because, honestly, screw luck. Luck had absolutely nothing to do with it. Decades of good engineering, planning, and following the bloody checklist are why this was a serious disaster and not a nation-ending catastrophe like it would have been in many, many other places."

This is fantastic and worth repeating. Thank you.

They're all very simple grids, which is the beauty of it. You could put them together in a couple minutes with something like 960gs or Blueprint.

Isn't that the benefit gained from testing, rather than BDD?

Might I suggest Jammit? You can write a rake task that packages all the assets, uploads the files to s3 and deletes the asset folder. Change the asset host to your s3 bucket or Cloudfront. Whenever you deploy, do 'rake deploy:assets' and you're set.

http://documentcloud.github.com/jammit/

The creepiness probably has more to do with their color choice and cut out triangle than the shape of it. Their model makes it look more sinister than a ball with ribbons taped on to it.

For me, though, it gets disturbing when you think about how many people are killed by what's on your screen.

Honest question: which browsers can't handle gzip'd responses?

Since you added PayPal, you might as well throw Braintree in there. It's pretty great. I've been happy using it for an app I'm working on. Oh, and Mailchimp's API, too. I have a feeling that this list is going to go on and on.

http://www.braintreepaymentsolutions.com/gateway/api

http://apidocs.mailchimp.com/

I doubt that most people expect the site owner to find their IP address (let alone what an IP address even is and what we can do with it) or what page they came from. When I bring up analytics with normal people, they tend to be a bit shocked.

I just set up Braintree and it was very easy. Probably not as easy as PayPal + Spreedly, though. If you want to go with a "real" payment gateway, I highly recommend it.

If anything, using Braintree removed all sorts of restrictions. They keep all the credit card information. Let them worry about PCI Compliance, not me.

Really? If you are serious about your startup, you should waste hours on a Coming Soon page instead of spending them on your product? Drop the few dollars on a service like this and get it other with.

This looks like a more ambitious version of something I worked on a little bit ago. Hopefully it works out for them. I think the key is to add features that developers normally wouldn't add if they made the page themselves (nice dashboard, populating a newsletter, sharing stuff, etc). It seems like that's exactly what LaunchRock is doing.

Until it redirects you to:

http://www.nyc.gov/portal/site/nycgov/?front_door=true

After watching a little bit, its reputation seems unfounded. To anyone interested in streaming:

http://english.aljazeera.net/watch_now/

To change the font, go to Preferences > User File Preferences and paste this in there:

  "font_face": "Monaco",
  "font_size": 13

I think there might be Wordpress addons that do this. It looks like Patrick's blog (http://www.kalzumeus.com/) uses one and I've seen a few other blogs with the same thing. It's annoying.

I usually use padding on an element to show a background image to the left of it, but the pseudo background-crop looks pretty great. Definitely going to use that one.

Is there anything stopping me from animating the background rotation with jQuery? That would add to the accordion effect if it works.

Oh, whoops, I didn't notice you wrote Katana. Hopefully my comment didn't seem like I was trying to take anything away from your gem.

I'm tempted to give Katana a shot with my next app. Who knows, I might like it more.

Might I suggest "herogit"? You can keep doing "heroku <command>" like normal – it just treats different branches as different apps, which I quite like. They put it in the last newsletter.

For example, I have a "staging" branch for my staging app and use the "master" branch for production. When I checkout the staging branch, the heroku gem switches everything to the staging app. Checkout the master branch and it switches to my production app.

(A little gotcha: I have to use "git push <repo> staging:master" to deploy the staging branch)

I've never tried the Katana gem, though, so I have no idea if it's better or worse.

https://github.com/jbarnette/herogit

There's always QuietURL for Firefox, which converts text to a link when you hover over it.

It's nice to have.

This flowchart might clear up the rendering differences: http://typophile.com/node/70216

It's not so much that rendering a whole bunch of text takes a while (though it might, but it probably has more to do with the time it takes to download the font), but more that the letters look different depending on who looks at it.

After that, it's up to the designer to decide whether or not the difference is acceptable. I'd say it works out fine in pretty much all cases. Your site doesn't have to look the same in all browsers, people.