HNHacker News
TopNewBestAskShowJobs

bcrescimanno

2,542 karma · joined September 28, 2009

Brian Crescimanno https://www.linkedin.com/in/briancrescimanno

Director of Engineering at Shopify

submissionscomments
bcrescimanno··on MailerJS: Send email with client-side JavaScript
Flagging for an incredibly misleading topic / tagline. This isn't actually "sending email with client-side javascript;" it's simply a script that allows you to send a message to a service that will generate an email for you. Seriously, it's basically a scripted email form--how this at all interesting?
bcrescimanno··on Backbone Events vs. Ember Bindings: A Benchmark
Not having worked with SproutCore, I honestly can't comment on whether it introduced more bugs. Working with anything async is always going to introduce some complexity; but given the poor DOM performance on low-end devices, deferring rendering is often a very helpful concept.

I'd be interested to hear what type of bugs were common in this scenario; my understanding of the runloop is that after the DOM update (at the end of each loop) the UI should reflect the application state.

bcrescimanno··on Backbone Events vs. Ember Bindings: A Benchmark
I think it's worth noting, that Backbone (as expected, I imagine) gives you a little more rope to hang yourself with here. To me, that's a great highlight of how the frameworks differ in their approach. "Perfectly written" Backbone code is significantly faster; but, if you (perhaps unknowingly) take a slower path, Backbone isn't going to do anything to make it faster. Not advocating one approach over the other; just pointing out the juxtaposition.
bcrescimanno··on Another Xcode Version, Another Example of Crappy Apple QA
I don't use XCode regularly--so I honestly wouldn't know. If the rant was about that constant crashing, I wouldn't have said anything.
bcrescimanno··on Another Xcode Version, Another Example of Crappy Apple QA
Flagging as trolling...and then taking the troll-bait.

All software ships with bugs--including the software this guy will create using XCode. Despite that, this type of drivel is still common among software developers. "One (relatively minor) bug exists that happens to annoy me: that must mean their whole QA process is shit!"

Come off it; this type of rant would be warranted if XCode routinely crashed when you paste a paragraph of text into a label--not because it behaves in a funky way.

bcrescimanno··on JSHint, A JavaScript Code Quality Tool
John Carmack wrote a great blog post a while back about Static Code Analysis.

http://altdevblogaday.com/2011/12/24/static-code-analysis/

While not all of this is immediately applicable to JSHint and the like, it provides some insight into why static code analysis can be seen as helpful.

As you also mention, it's really helpful for code within a codebase to be consistently written. JSHint can help enforce some of that consistency. This is where JSHint really shines.

If your JS is tied to some sort of "build" process (even a short 1-2 second one), catching errors before running the build is incredibly helpful. If you intend to minify your JS code (as you should) before distribution, finding missing semicolons can be very important, indeed. I find the most helpful JSHint errors to be about mistyped variable names. It's so much easier to see that in my editor, fix it, and THEN run it in the browser.

bcrescimanno··on JSHint, A JavaScript Code Quality Tool
You might check out Syntastic. It supports JSHint if you have it installed and also supports other languages. I switched to it after using the JSHint plugin for a while.

https://github.com/scrooloose/syntastic

bcrescimanno··on Backbone vs Ember
It really depends on your environment and the complexity of the rendering tied to your collection. For example, on a fast desktop-class system with a collection that renders one element with 1 property, you can probably have hundreds (or maybe even thousands) of items in the collection before you start to notice slowdowns when the collections update. Working on lower-end and mobile platforms, those numbers change. Similarly, if you rendering is complex, it will take more time as well. All that said, there's really no "magic number"

There are definite workarounds such as setting up paging--but the simple approach of using Ember.js bindings to bind a collection to a template will fall to pieces as that collection grows.

bcrescimanno··on Backbone vs Ember
There are some pretty legitimate concerns with Ember and large data sets right now as the treatment of those datasets tends to be fairly naive and linear. There are several people, myself included, who are working on ways to address that problem--but modifying a large collection, at the moment, can trigger the entire collection to re-render which can be extremely expensive.

FWIW, I'm not an expert on Ember.js or Backbone; just someone trying his hand at hacking the Ember.js code to work more effectively with collections (since some of the use cases I have would be impossible using the current methods of bindings and collections).

bcrescimanno··on Ruby 1.9.3 via RVM on Mac OSX Lion: Success Story
I was really hoping this was someone talking about making Ruby 1.9.3 compile with llvm-gcc. At home, I'm running ruby compiled with clang and I've noticed the occasional hiccup with some gems. But, unlike the author, I do use software installed with XCode (iOS dev kit) so uninstalling XCode isn't really an option.

For what it's worth, there are a ton of recommendations to do this same thing out there--and for many people it's just not a viable option. This isn't a success story so much as it's using a workaround. Not being part of either the Ruby or Apple dev teams, I won't say whose side this is on to fix: only that it needs to be fixed.

bcrescimanno··on Ask HN: JavaScript Dev Tools
It's not that it's long, it's that it has to be done at all. Even without a build process (or one like ours that takes at most 5-10 seconds) it still takes longer than finding the line of code you're concerned about and setting a breakpoint within the debugger itself.

To each there own as to how setting breakpoints works best for them in their workflow--my only reason for commenting was to let people know there were other ways to set breakpoints than adding "debugger" lines all over their code.

bcrescimanno··on Ask HN: JavaScript Dev Tools
Well that was actually my point; JSHint is effectively a highly configurable version of JSLint.
bcrescimanno··on Ask HN: JavaScript Dev Tools
The problem is that JSLint goes further than static analysis and suggests what could be considered simply "stylistic" changes to match the way Crockford thinks javascript should be written.

For example, doing comparisons (x == null) or (x != null) is a well known shortcut for checking vs null or undefined. There's nothing inherently "bad" about using that shortcut.

bcrescimanno··on Ask HN: JavaScript Dev Tools
Breakpoints, yes. But many folks (myself included) set the breakpoints in the debugger itself--you don't have to put that line into your code to set a breakpoint.

Since some folks write JS that has to go through a "build" process, it's easier to set a breakpoint in the debugger than to go back, modify the code, and "re-build" to get a breakpoint.

bcrescimanno··on Use Facebook and LinkedIn to find an airline seatmate goes live: KLM Meet & Seat
I hate to say it; but my prediction for the use of this service goes about like this:

Several young, socially connected folks give it a shot.

Horny dudes browse the passenger list looking for a "hot chick" to sit next to.

Girls wise up to what the guys are doing and stop signing up.

Guys do what we always do and lose interest in yet another "social activity" completely devoid of women.

bcrescimanno··on This photograph is free
Not to digress too much from your original comment (which I completely agree with) but I think there's a certain "smugness" that I see associated with people who release anything as free--as if somehow the act of benevolence has put them on a plane above those who choose not to. I think that's unfortunate for multiple reasons; not the least of which is that people should be commended for sharing things under free / open licenses and I'm far less inclined to do so if they get all smug about it (this applies whether the "things" in question are software, photographs, writings, music, film, etc).

I agree with both authors; but I find this particular article far more obnoxious than the one to which its responding--again, because it comes across quite smug.

bcrescimanno··on Why do we pay sales commissions?
There isn't a difference; your post (to me) implied that people working on more complex deals should be more highly rewarded. My argument is more that removal of commission-based compensation doesn't necessarily remove the concept of reward for hard work. All it does is decouple it from each individual sale. Better people who work better / smarter (should) still be compensated appropriately.

I completely agree with your assessment of sales commissions elsewhere--and I think we've all seen enough of a share of unfair, incompetent management to understand the rationale. That said, I also agree that there is some serious baggage that comes with commission-based compensation and it's worth a look to dump it.

bcrescimanno··on Why do we pay sales commissions?
I disagree with your edit; with the quick adage that it's far easier and cheaper to retain a customer than create a new one. It sounds to me like Fog Creek has a mix between sales and account management (but so do a lot of companies that I've come across). If your sales team is also working in that account management role, retaining their clients should always be high priority even if those customers wont' be up for renewal / another contract for some time.

Moreover (and I'm reading between the lines a bit here) I think part of that statement is referring to sales people ignoring the "hard" sales and focusing only on the "easy" sales. "Are you ready to buy? No? Ok, I'll call again in 6 months" becomes, "Let's talk about your concerns so that maybe you'll buy in a month instead of 6."

bcrescimanno··on Why do we pay sales commissions?
I agree with your thinking that some sales folks might balk at the notion; but I'm not sure I follow your argument you should be directly (financially) rewarded for the additional effort in the larger deal. I've known several sales folks who chase many small deals simply because they're a lot easier to manage, require less time to close, and by collecting as many of them as possible, they're able to maximize their commissions.

My thought is that, just like in every other aspect of the business, your top players will be your highest paid as part of the normal compensation process--and those top people should be the ones closing the bigger deals. Just because you don't get cut a check for that specific deal doesn't mean there wouldn't be rewards for doing so.

bcrescimanno··on Bill Joy's greatest gift to man – the vi editor
Actually, it's from 2003 but the entirety of the interview is from 1999. I had that issue of Linux Magazine and I remember reading the interview back then. Sad that it took me over 10 years to really dig into vim after reading about the history of vi.
bcrescimanno··on Download.com Response to Nmap Offer Bundling
Translation: We go through a rigorous process to ensure that we don't give you any spyware / adware / malware...

...except, of course, our own.

bcrescimanno··on "Prototype.js and Mootools did not break the web"
Part of the difficulty with the dogma surrounding the issue of whether or not it's ok to extend built-in objects comes from extrapolating a set of guidelines and rules for library / framework developers to everyone else. There's real value in libraries not extending built-in objects simply because they can't make any real guarantees about their execution environment and shouldn't force their customizations on all code in that environment.

I think part of it comes from the most vocal (and probably most respected) JS developers tend to be library developers and their guidelines for themselves and each other tend to get misconstrued as general guidelines for JS development.

When you're developing in a known execution environment, I don't see any particular issue with extending natives.

bcrescimanno··on How Google did their barrel roll trick
Out of curiosity: why is the fact that this effect was achieved with a few simple lines of CSS3 (whether it was keyframe animations or simply a rotate transition doesn't really matter) front page news? Maybe I'm just jaded because I'm a UI engineer--but the "trick" wasn't particularly impressive (though it was quite amusing--and would have been even more so if they'd used HTML5 audio to get Slippy Toad in there).
bcrescimanno··on Groupon shares open up 40%
I'm absolutely unsurprised that the shares were sharply up on the open; IPOs over the past decade have mostly turned into government-sanctioned (or at least ignored) "pump-and-dump" operations. One of the things I've come to despite having moved to Silicon Valley is this absolutely infantile obsession with by-the-minute stock prices.

Congrats to Groupon on their successful IPO; I still have very strong doubts that they have any means of building a successful, sustainable business. Time will tell better than my attempts at fortune-telling.

bcrescimanno··on Famous Logos Designed Entirely in CSS
Totally fair; and I wasn't intending to pick on this example in particular. However, I see a lot of this "look at this amazing shit we pulled with CSS" that's generally inapplicable beyond their (admittedly cool) example.
bcrescimanno··on Famous Logos Designed Entirely in CSS
That's cutting a pretty broad swath there; CSS does not necessarily render more quickly than images--especially on low-end devices. For example, things like drop shadows are incredibly slow to draw in CSS on low-end devices whereas downloading and rendering a properly compressed 1kb png is significantly faster.

It also depends heavily on the complexity of the logo and the painting implications. To say simply that "CSS will be more performant" is categorically incorrect.

bcrescimanno··on Famous Logos Designed Entirely in CSS
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry!

It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post over and over again.

I can hear the arguments now, "but it shows off the power of CSS!"

No, it doesn't. It shows off what a clever person can achieve by tinkering with a system; but there's no practical value to most of the techniques demonstrated. CSS has a lot of power; but its best demonstrated by projects like the CSS Zen Garden that show off real-world CSS use.

bcrescimanno··on Steve Jobs Worked on Apple Until His Last Day
Simply google "steve jobs death certificate" and you'll find copies of it everywhere.
bcrescimanno··on Steve Jobs Worked on Apple Until His Last Day
And I think your interpretation is far more likely. As much as I know everyone wants to believe that Steve was involved until the very end; I've seen people in the final week (and final minutes--my grandfather) of pancreatic cancer. They're not "working" on much of anything other than taking their next breath.

It makes for one hell of a story; but, I think the better story is to think of a man who spent his last 24 hours alive with those closest to him--his family.

bcrescimanno··on Time to fork the FSF
I tweeted earlier that I see RMS as the Fred Phelps (Westboro Baptist Church) of Free Software. He may not have started out this way; but these days he's completely single issue. If you're not doing free software 100% his way; you not only disagree with him but you are actually evil. Not just free software; but free software as RMS defines it(see GNU/Linux) or you're wrong. He's so blinded by his own zealotry that I'd argue that beyond the inner, hard-core "free software circle, he's seen as much of an embarrassment to the notion of free software as Phelps and Westboro are likely seen by other Christians.

I've felt this way a long time about RMS; his comment about Steve Jobs's death was uncalled for--but it really was well-within character. Just like Phelps and Westboro are expected to show up at soldier's funerals to protest, we've come to expect this type of shit from RMS--and I agree with the OP that it's time to stop just accepting it.

[Edit] I want to state that RMS, like everyone, is fully entitled to his opinion and that opinion carries no more or less weight than my own. Moreover, you're completely entitled to agree with him. What I do have a problem with is what the OP described: he doesn't belong at the head of a major organization, nor does he belong at the apex of the free software movement. Beyond my earlier described "inner circle," in the past several years, he's done more to tarnish the image of the free software community than to help it.

← PreviousPage 9 of 13Next →