1,402 karma · joined August 1, 2011
Email: kevinconroy [at] gmail [dot] com
<!-- Async Tracking Code - http://code.google.com/intl/en-US/apis/analytics/docs/tracking/asyncTracking.html -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'YOUR ANALYTICS ID GOES HERE']);
_gaq.push(['_trackPageview']);
//*******************
// Trick #1: Track page load time in Google Analytics
// (note: only works for HTML5 browsers)
//*******************
_gaq.push(['_trackPageLoadTime']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
//*******************
// Trick #2: Add a Javascript error handler so that it creates an event in Google Analytics
// whenever there's a CLIENT-SIDE javascript error
//*******************
window.onerror = function(message, file, line) {
var sFormattedMessage = '[' + file + ' (' + line + ')] ' + message;
_gaq.push(['_trackEvent', 'Errors', 'Browser', sFormattedMessage, null, true]);
}
</script>
Update: Included complete GA code to address any confusion on order and values available in stack.What happens when the product is released? What's the pain that you're taking away from me in the future so that I want to use your product now?
Low-tech is the most reliable solution here. Print out key passwords, instructions, etc and store them with your will. You can include instructions in here about how to access stuff like Deadmanswitch, LastPass, etc, but for everyone's sanity, print out key passwords as well.
Yes, this creates a security hole. You need to weigh that against the desire to ensure that your significant other can easily access this information in case of your demise.
(If you want to make this a bit more foolproof, print out a simple ciphered version where you agree to replace one character with another (e.g. replace the last initial of your name with the first initial) but then again, if your significant other can figure out a simple cipher, they can probably handle the electronic systems...)
Remember Kathy Sierra's advice: Don't buy this because we kick ass, buy this because we want YOU to kick ass.
http://headrush.typepad.com/photos/uncategorized/2007/04/06/...
The lesson you should take away from Ben isn't how to respond to unfair post - it's that you should be always open to communication (positive or negative) and that you should respond as a polite, respectful human, not as a "company" voice.
As a result of my interactions with Ben and his incredible product, I'm a loyal MailChimp user and regularly recommend them to people looking to setup newsletters for their companies.
http://www.campaignmonitor.com/css/
I've also found Litmus to be an incredible resource for cross-client test (Outlook vs Gmail vs Yahoo! vs ....). If you send a lot of emails as a part of your user retention strateg it's vital that you test this. You'll be amazed at how different they look and how a few hours of tweaking can optimize things across a large number of clients.
I know that After Effects was used to make one of the best animated videos out there: http://www.girleffect.org/
There are always a thousand things that you can prematurely optimize (page load time, HTML, conversions, etc). The trick is figuring out what the highest ROI thing is for you to optimize right now given your specific point in time. If you get 100 visits/day set metrics around sign up, retention, or whatever is going to build you up to 1K/day. Then figure out how to get to 10K/day, and so on.
Seems like in most scenarios you're getting at best 40% energy efficiency in gasoline engines and somewhere between 17% to 40% in steam engines.
Even at 17% efficiency using the sun to generate steam power seems to hold lots of potential. The trick will be to get it working at scale and able to produce a similar level of energy with the same or lower cost as existing technologies. May be a while yet, but it's an exciting time to teach your kids science as this is the kind of stuff that they'll probably see in mass later in life.
Should it be fixed? Ideally yes. But in the real world, it depends.
Is the user billed hourly (and therefore do they want you to fix it)? What's the business context? Will it help other users? (Are there other users?) What is the app doing in those 8 minutes and how would reducing it affect (positively or negatively) the user experience after startup?
Yes, getting a faster start time is ideal, but assuming limited resources you need to figure out what the biggest user experience problems are and fix those first.
If you application takes 8 minutes to load, the biggest user problem may well exist AFTER the application has loaded. Fix that first.
If the candidate is strong, then I send them links to job openings at some of our peers, partners, and even competitors (depending on skills). Sometimes we get people who are solid technically but just not the right fit for our culture or team. In this case, they may be a good fit for another team. Your meta goal is to get strong candidates to work in the larger ecosystem that surrounds your company, not just your team.
This extra step always surprises and delights candidates, even if they don't end following through. They'll then go on to think and say great things about your company.
It's an incredibly nice thing to do that will pay dividends. I'm Twitter "friends" with several candidates we passed on by took this approach with. It's lead to several business development meetings, a partnership, and evening a speaking engagement. They've also referred new candidates to us.
I've had nothing but win from this and strong encourage others to try it.
Same holds for your email marketing, social media, etc. Good content is an order of magnitude more important than time-of-day optimizations (which in my experience, only helps some people some of the time).
I think all languages have strengths and weaknesses that matter based on the context.
For example, I hate manually managing memory in C/C++. Java, Ruby, etc automate all of that for you, but it comes at a cost of using a lot more memory. That's not a big concern for many applications, but if you're doing embedded software or real-time systems it can be a deal breaker.
So in this example, is C++ better or worse than Java? The answer is that it depends what problem you're trying to solve, what environment you're running in, and what resources you have available on your development team. Personal preference matters too in terms of programmer satisfaction, but just because you like one language's constructs more than another doesn't mean it's well suited to every problem space.
As to the original article, I think it's great to learn about how different companies change their software stack, but not because "w00t Twitter hates Ruby - Java rocks"; rather it's interesting to see how business context changes over time and the implications that has on the technology. Seeing how other businesses have dealt with these hurdles can help you keep an eye out for them in your own business. I just wish that this was the lens that it was written in rather than "OMG - Ruby = Fail Whale."
If you're a language designer then it's good to hear about the complaints and preferences of programmers so that you can design a better language (and thus a better tool). And like any tool, there will be times when it's better to use one language rather than another.
The wise programmer says: "Use the right tool for the job."
Please HN, we're wiser than trending stories would suggest.
I agree that this is a larger problem in the industry, but I meant no offense.
In my experience, though, I've found that it's very natural to integrate graphic and UX design into sprints along side programmers. As the Product Owner, my goal has been to keep a rough roadmap of issues and features. I often schedule design or graphic work a sprint or two ahead of when we want development to occur. In this way, the requirements become more fully baked in advance of coding. If design or UX uncovers issues that cannot be solved by the end of the month that's okay. Just reevaluate during sprint review and determine next steps. Usually giving them another sprint provides enough time to figure things out.
Another trick is to have developers create a working "wireframe" version of features in the template language. (Think HTML with CSS turned off in your browser.) Then when it's working, hand it off to the designer to make it pretty in the next sprint. Doesn't work for every feature, but small to medium sized ones can benefit from this. This also provides a good way to handle scheduling contention so that the designer doesn't have to handle every issue before developers do.
Your milage may vary, but I've have 95%+ success with this technique.
GlobalGiving - http://www.globalgiving.org/aboutus/jobs/software-engineer-f...
DonorsChoose.org - http://www.donorschoose.org/blog/category/job-opportunities/
Kiva - http://www.kiva.org/jobs
charity:water - http://www.charitywater.org/about/jobs.php
Volunteer Match - http://www.volunteermatch.org/careers/
And thousands more at http://www.idealist.org/
Pro tip: Set up monitoring alerts on your SSL certs to alert your sys admin when they are getting close.
For example, here's a Nagios SSL expiration alert: http://exchange.nagios.org/directory/Plugins/Network-Protoco...
Certainly stay hungry, stay foolish, stay passionate. But keep iterating in all things.