bryanmig

After using an email-based homegrown solution that I thought was sufficient, I gave RayGun.io a shot. I use it for .NET exception tracking and I am about to wire it up to a Rails app, and a very very large Backbone JS application.

It is really quite good (at least for .NET). The management UI is great and does a very nice job of grouping duplicates, similar issues, etc.

I already use some dev tools from Mindscape (their .NET ORM, LightSpeed) and their products and support are top notch in my experience.

http://raygun.io

This isnt that big a deal. They say that you can opt out of this and that it does not apply to Fios or Business customers.

I'm sure there is a huge amount of customers who will never have any clue that anything has changed since they dont play games, run servers, need VPNs, etc.

It's probably a good thing for everyone else given that it does raise even more awareness of the problem.

Client side: jQuery, SASS, Backbone.js, JS written in CoffeeScript. AngularJS for our internal administration app.

Server side: ASP.NET MVC 4, Ninject IoC, LightSpeed (amazing super fast ORM from Mindscape, not free)

Infrastructure: Amazon AWS (EC2, S3, CloudFront), SendGrid for email, RabbitMQ, MySQL 5.6, MongoDB (for realtime stats)

Admittedly, I dont know anything about the law but I have a couple of questions:

1) If convicted, would that have set some precedent that could have affected others for years to come?

2) If the "Suggest of Death" papers were filed, does that mean that the courts cannot convict him of any wrong doing, thus preventing any precedent from being set?

(Though it sounds like one.. this is not a conspiracy theory.. just a legitimate question)

NYC - Full time - iOS and Android developers

FieldLens

We are hiring both an in-house Android developer and iOS developer for FieldLens, a venture-backed startup in the heart of Manhattan’s Flatiron district. You'll be responsible developing new features and iterating and maintaining our existing application.

Our Android application currently specified for API Level 8 (Android 2.2) and up.

Our iOS application is being built for iPhone using iOS 5, uses Core Data for local storage. After launching on iPhone we will target iPad as a universal application.

FieldLens is a technology startup focused on bringing a beautifully designed enterprise solution to the construction industry. Our application is a fully-networked solution with robust back-end services driving functionality across any platform. Designed mobile-first around the actual needs of the construction professional, our mobile applications work completely offline. It’s time for the awesomeness of apps to change a big old broken industry. Join us and make it happen!

We’ve got a great team and work in an awesome shared workspace in the thick of the NYC startup scene. Over the past several months we’ve been building Version 1.0 and are headed into beta soon. Recently seed funded, its now time to build out the team. No annoying management meetings, no dress code, and there is a beer bottle (with the FieldLens logo) on our dev team’s desk. We work our butts off but also know how to have fun.

We'd like you to have the following skills: - Experience with SQLite databases, JSON and RESTful web services (Spring framework) preferred - Seriously good OOP skills - Solid Java or Objective-C

Sound interesting? Shoot an email over to matt at fieldlens.com

True and untrue.

I use MongoDB for my startup (yabblr.com) and have quite a relationship data stored in my entities.

For example, my user entites have an array of commentId's stored inside of them.

Whenever I fetch 1 or 1000 users from the database, a framework that i designed will look at the entire list of users and build a single list of commentIds based on that list.

Then I do one more lookup on the database to find all comments in my new list of comments.

Then a final pass over the users looks up the commentId associations and inserts the actual comment object into the user object.

Finally the list is passed back to the consumer. Its 2 database calls. It does require that there are 2 iterations over the first call (one to gather up comment Ids and one to associate comments with users) but since its being done in the application layer, its much easier to scale.

The point is that when your table has 4 rows in it, it doesn't matter if you do a full table scan. Wait until you deploy your app and that table now has 4,000,000 rows in it.. then you have a problem.

In MongoDB (and maybe others too) there exists an option to fail when doing a table scan so that you know immediately while developing that there exists a potential for things to go awry at some later point. You can fix that now by either re-thinking your data structure, re-thinking your query, or adding appropriate indexes.

MySQL's slow query log is good for reactive development instead of proactive development.

I think its an indispensable feature.

I've used Bugzilla, Mantis and Jira.

Jira, while not free, is the best of those three for sure. They have a nice $10 for 10 user license that is quite affordable and besides the 10 user limit, has no functional limitations.

I've read good things about FogBugz but have not used it myself.

The ability to pick and choose the components that make up my workstation - laptop, monitor, etc. I hate being given a laptop that I dont like upon joining. Or worse, being given a laptop used by the guy before me.

Proof that hipsters are taking over the world.

I bought a Palm Pre (1) for Sprint about a month after it came out. I still think the operating system, WebOS, is great but Palm really let me down with the device. It was just pure crap.

Despite its sleek design, the craftsmanship was poor and the phone cracked in multiple places. The plastic screen also scratched very easily.

The worst part of it all is that the phone is underpowered. The processor is slower and has less RAM than its competition. This is why the phone performed so poorly despite having a great operating system.

I hope HP can make the next generation WebOS powered devices perform better because it really is a great OS.

So a guy who is an expert in Clustrix (and knows how to setup, tune, etc) compares it against some other technology that he does not know (and does not know how to setup, tune, etc) and comes to the surprising realization that his technology is better?

Where have I seen this before? Oh right.. every time I see "Technology A vs Technology B" comparisons.

Naturally his results are in his favor, otherwise he would not have posted them.