werkshy

  "This is pre-alpha quality software, the result of a three
  day project. It will crash your browser, leak your
  passwords and destroy your home. This is actually my first
  Chrome extension and I am no expert javascript programmer."

It's written in Ruby but is not really dependent on Rails or anything to run. We use it to compare a list of URLs between the version we are currently testing in CircleCI and our production site. Any differences are highlighted in a nice gallery and we get a message in our Hipchat room.

  ubuntu@c1-10-1-18-157:~$ sysbench --test=cpu --cpu-max-prime=2000 --num-threads=4 run                                                                           
  sysbench 0.4.12:  multi-threaded system evaluation benchmark                    
                                                                                
  Running the test with following options:                                        
  Number of threads: 4                                                            
                                                                                
  Doing CPU performance benchmark                                                 
                                                                                
  Threads started!                                                                
  Done.                                                                           
                                                                                
  Maximum prime number checked in CPU test: 2000                                  
                                                                                
                                                                                
  Test execution summary:                                                         
      total time:                          6.7674s                                
      total number of events:              10000                                  
      total time taken by event execution: 27.0485                                
      per-request statistics:                                                     
           min:                                  2.69ms                           
           avg:                                  2.70ms                           
           max:                                  7.00ms                           
           approx.  95 percentile:               2.70ms                           
                                                                                
  Threads fairness:                                                               
      events (avg/stddev):           2500.0000/17.36                              
      execution time (avg/stddev):   6.7621/0.00

Of course, we are a Rails shop who have been on Heroku since we launched, so Heroku is really tailor made for us. If you're happy on raw AWS, good for you. Every hour I'm not thinking about AWS is an hour I can be writing a feature for our 10-month-old startup. The extra cost of Heroku is negligible when viewed in that light.

We first conceived of Dynosaur as a plugin-based autoscaler (with GA and New Relic plugins to start with), but we've found the times we really need to scale fast are the times we have a lot of traffic generated from press stories etc (like this from today, if you will excuse the shameless plug: http://dealbook.nytimes.com/2014/01/21/a-start-up-run-by-fri...) and using the analytics live API allows us to react a little quicker than if we waited for New Relic to tell us our response times are getting slow. So far, we're happy enough with just a Google Analytics plugin.

One possible improvement would be to scale differently based on different traffic / performance metrics across the site. I think New Relic or other performance instrumentation would be very useful for that.

No offense intended: you picked a cool name!

Our main motivation was to write something that scaled as we scale manually (i.e. when we get a lot of traffic due to press hits etc, we scale up based on GA realtime data as well as New Relic response times). When we were given access to the GA live API it just seemed like a natural fit.

As a phone, I need to use the number line a lot. As a computer /terminal, I need to use letters, numbers & symbols a lot. 3 and 4 row keyboards are bad for both of these use cases.

If someone makes a decent, interesting 5-row qwerty phone, I will buy it tomorrow.

We're building a platform for controlling residential energy usage (think wifi thermostats, but also all sorts of home automation stuff). We're looking for a smart someone to work on all aspects of our software platform, from the back end, to web and mobile applications, to the tools that we use in development and production environments. We’re a small team, we use Python/Java/Backbone/Mongo/lots of other stuff and we're open to new ideas.

In addition to solving all of the usual software problems (achieving high availability, dealing with lots of data, implementing web services efficiently, choosing the best JS and CSS technologies, etc.), we also deal with real physical devices, so you will be encouraged to learn about boot loaders, Z-Wave, how to conserve the battery of an embedded device, and much more.

We're well funded, have a great workplace environment nestled between artist studios in Brooklyn and I think you'll like the team.

http://www.energyhub.com

Apply here or contact me informally for more info (email in my profile): http://careers.stackoverflow.com/jobs/21403/full-stack-devel...

It's hours and days wasted, and that's before I consider any difference in productivity while actually using each IDE. If any of this sounds familiar, do spend a couple of weeks in the free version of IDEA. It was night-and-day for me. The worst part will be your muscle memory (e.g. stepping through the debugger).

The 2GB 32-bit limit of MongoDB seems like a complete non-issue to me.

  Wed Sep 19 17:29:21 [initandlisten] MongoDB starting : pid=3765 port=27017 dbpath=/var/lib/mongodb 32-bit host=deepthought
  Wed Sep 19 17:29:21 [initandlisten] 
  Wed Sep 19 17:29:21 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data
  Wed Sep 19 17:29:21 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations
  Wed Sep 19 17:29:21 [initandlisten] **       with --journal, the limit is lower
  Wed Sep 19 17:29:21 [initandlisten] 
  Wed Sep 19 17:29:21 [initandlisten] db version v2.2.0, pdfile version 4.5
  Wed Sep 19 17:29:21 [initandlisten] git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207
  Wed Sep 19 17:29:21 [initandlisten] build info: Linux domU-12-31-39-01-70-B4 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_49
  Wed Sep 19 17:29:21 [initandlisten] options: { config: "/etc/  mongodb.conf", dbpath: "/var/lib/mongodb", journal: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log" }
  Wed Sep 19 17:29:21 [initandlisten] journal dir=/var/lib/mongodb/journal
  Wed Sep 19 17:29:21 [initandlisten] recover : no journal files present, no recovery needed
  Wed Sep 19 17:29:21 [initandlisten] waiting for connections on port 27017
  Wed Sep 19 17:29:21 [websvr] admin web console waiting for connections on port 28017

We pay a lot to stay multi-AZ and it seems Amazon keep finding ways to show us their single points of failures.

But the first $ is wrong, it should read PS1="\[\033[G\]$PS1"

Nice to see CINT evolving and using clang for better conformance (and performance, presumably), and hopefully this will free some time that was being spent on CINT but if you find yourself using this more than once for physics analysis, do yourself a favor and try python instead.