unshift

yup. i'm working on a site for weddings and wanted a female perspective

i used this exact method to find the designer i hired about a month ago.

overall, it worked out, but it was a frustrating process. i was aiming for some specifics: a female designer who was up to date on HTML5/CSS3 and ideally had some wedding stuff in her portfolio.

i probably contacted no less than 25 people (through their websites) over the course of two weeks, and was met with either a lack of response, note saying they weren't accepting work, couldn't start soon enough, or for one reason or another i reconsidered.

eventually i found someone who is now doing some really great work, but it wasn't a fast process.

it's important to carefully check out portfolios, because while most things look good on Dribbble, a nice icon or logo doesn't necessarily translate into solid web design skill. i spent a lot of time validating pages (and pages linked in their portfolio), looking for design elements i liked and didn't like, and overall indications that they'd be good for me to work with. that way, once i hired my designer, i knew what to look out for (e.g. press the issue of validating HTML).

all in all -- Dribbble was a good place to find designers, but i still had to do diligence on my end to find the right one for my project. that's basically echoing the point of the article, but it's worth repeating.

I got the circle and after 8 tries on a trackpad I was unable to get it

i understand the case where you don't have a box with e.g. port 80 available and need to use their server as an endpoint, but otherwise is it really that hard to remember ssh -L and -R syntax as the article suggests?

i also don't really see where you'd need to tunnel and serve production traffic from your dev machine versus having a proper staging environment and testing there. that has "bad idea" written all over it.

> we’re all starting to see the benefits of having a production-like environment right there on your laptop so you can iteratively code and debug your app without deploying live, or even needing the Internet.

actually, real professionals have seen these benefits for ages. that is SOP for good programmers.

the fine folks writing the Twisted Python library solved this problem years ago with the Deferred abstraction and the @inlineCallback decorator. there's a little bit of a performance penalty but an enormously huge increase in code readability.

i wonder why they don't just go to a date based approach. 2.2 and 2.4 were different, 2.4 and 2.6 were different, but within the minor 2.6 versions they've made some (what i would consider) pretty big changes without bumping the version number accordingly.

they seem to have abandoned odds/evens branch structure in favor of something a little more continuous, which is great, i just wonder why they don't ditch the old numbering scheme as well.

is it stored as plain-text in the database?

Localytics is over in Cambridge, amongst a few others. http://www.localytics.com

sorry but that seems really naive. an SLA is not a guarantee of service -- you can't force a computer or network to stay online because someone with a sheet of paper said so. it's a target for a best-effort guarantee and when that guarantee is broken then you get a bit of a refund.

it's like when you have a big building project and there's a provision that the contractor will refund $5000/day for every day past march 1st. doesn't mean march 1st never gets passed.

failure modes in the cloud are known too: your VMs are either working or they aren't, or maybe they're somehow degraded but you should fail over anyway. it's very similar to physical hardware. what will you think when a backhoe takes out your datacenter's fiber for 10 hours? that physical hardware and datacenters are now unreliable too?

as for a database that runs on a system that offers no guarantees -- isn't that all of them?

sorry, this is probably tangential, but how is the AWS outage any different from any other hardware outage, regardless of whether or not you actually own the hardware?

why does it seem that everyone expects 100% uptime from a VM just because it's in "the cloud"? shouldn't "the cloud" be used to make fault-tolerance even easier, because you have access to multiple geographic regions and multiple providers with little fuss?

they're still computers, and they're still bound to go down occasionally. i don't see how running leased VMs somehow absolves you of doing basic operations work and guarantees a bulletproof experience. regardless of where you host it, writing a nicely distributed and fault-tolerant system is and always has been difficult. the only part that's gotten easier is finding rack space.

just because you're trying to improve doesn't mean you have to share your bad code with the world.

there's nothing wrong with writing code and trying to improve, but there's something to be said for being a good editor and not releasing every keystroke you type. why release that which isn't good or useful?

disagree with releasing a project every week. what makes a project worth using is continued maintenance, thorough tests, comprehensiveness, and battle-tested API; not just a few snippets of code you uploaded somewhere on a sunday.

I agree with you.

I spent about two weeks looking for a designer who worked with both wedding stationery and websites. I found a few that basically did one and dabbled in the other, but didn't find anybody who thought they could do the job. In the interest of launching something to get some feedback, I just did it myself.

Time to start looking again, though. Now that the site is up and I can add users to something functional, I should get back to making it actually look good.

Thanks for the feedback!

Asm/C and Java/scala are unfair comparisons, since they're totally different languages with different structures and idioms.

I just started using CoffeeScript for a project of mine and while it did clean up the messy look of the Javascript, it doesn't improve much upon Javascript feature-wise. I felt like I was still writing Javascript, it just looked a little better.

your hands need to be near the tool in a mill for a couple of reasons, including clearing chips and applying oil/coolant.

also when you zero out a mill, you need to touch off a tool (don't know the name) to define your origin spot. it's not sharp and you should spin it at low RPM, but it's still moving, and you shouldn't have gloves anywhere near it.

transitioning? they've had over 20,000 employees for a few years now. you cease to be a startup after you've started up. for them that probably happened around 1998-2000.

I worked at a machine shop as a teenager and the machinist there always said, "you computer guys have it easy. You make a mistake, you just press backspace. If I make a mistake with one of these machines it's either going to cost a couple grand or I'll need a new hand."

not being a jerk but i don't actually get it -- i can post something that i need and a price and then what? people people can say they need it too? why do i care?

a few nits:

- your URL scheme is no good (/projects/<number>), should be something more readable

- the footer should read, "bear with us, we have cool things brewing" and not "we got"

- your homepage doesn't actually explain what effect "gropling" something has, if any

> In fact you can make yourself a fairly decent retirement for a latte a day.

not really. $3 * (40*365) = $43,800. in order to save $1M over 40 years, you need to save $2083 a month. and $1M is not a glorious retirement.

no. if you're scanning for open ssh ports you just scan IP blocks, not host names.

the only piece of solid, indisputable resume advice i've heard is to never, ever send it to anybody in MS Word .doc format. only in pdf. otherwise all sorts of recruiting agencies will add and subtract things before sending it out, which typically results in the whole thing being a huge waste of time for you.

even better advice is to avoid agencies all together.

A: was the 3.5" 1.44MB micro floppy as pictured in the video, B: was the 5.25" mini floppy

direct link to the video: http://www.youtube.com/watch?v=X4SCSGRVAQE

the idea is to validate all input only once, when it's transformed from raw user-input data into structs/objects/etc used by your program. after that, assume it's valid.

that's how all of those black friday deals work as well.

i've noticed these "culture" posts tend to come from people trying to set it, not people trying to live within it.

in my experience typical high-tech R&D department workplace culture is one of nerds who are technically extremely competent, but communication issues are very common and people tend to be passive-aggressive. one-upsmanship abounds. the culture expects long hours for no overtime, the "i'm here for a paycheck" attitude is frowned upon, and the work is not anywhere as cool as corporate propaganda makes it out to be.

i may be jaded but i don't see how some higher-up preaching about "aligning interests" and "being passionate" is actually affecting any real day-to-day issues.

a more honest article might be about hiring people who are similar to existing employees, in terms of personality and priorities. maybe you only want to hire people who like to work 24/7, or maybe people who want to "change the world" through gluing together webservice APIs, or maybe you just want warm bodies to fill chairs.* but i guess there's no patting yourself on the back there and it doesn't sound as cool as screening for "culture-fit".

* not a comment on wealthfront. I don't know what they do or how they operate. just a general observation.

i wouldn't call it exploitive, rather i would say it's very savvy. even if it's a one-time shot, it's real money and you're not doing anything shady to earn it. that's how people build wealth -- seizing opportunity. congrats on the success.

i think most (non-computer) people would consider that the reason for achieving status in the first place.

lmgtfy just issues a redirect, it doesn't perform a query and return results of its own

i don't see how... if my code requires foo.h and bar.c, but those get compiled and linked into one executable. how will running that program expose that?

moreover, how can you run strace to figure out dependencies on a program that hasn't been built yet? how does it determine when new dependencies are added?