New Relic Blog

Many Go programmers refer to themselves as Gophers actually after the mascot the same way university students might refer to them selves as Jaguars, Titians, or Aggies. It's hard to google a good example but here's one I found: > A creative and passionate community of Go developers and users (“Gophers”) has grown up around the language, and today there are U.S. Go conferences, European Go conferences, […] even a group for LGBT Gophers (yes, “Gayphers”). https://blog.newrelic.com/technology/golang-experts-follow-online/

If you're talking about widgets that track things like CDN performance and errors, like NewRelic's[1], then... maybe. I love that people are blocking tracking widgets, but there are some companies that provide useful gadgets that don't compromise privacy and I'd hate for them to be blocked as well. That said, I can't wait for Facebook tracking widgets to go away. 1) https://blog.newrelic.com/2014/03/13/javascript-error-reporting-ajax-t…

New Relic's CEO has some tips on how to keep coding: http://blog.newrelic.com/2014/03/11/sxsw-coding-ceo-recap/ 1. Surround yourself with amazing people. 2. Carve out specific times for development work. 3. Focus on high-value projects. 4. Make it clear why a coding CEO is good for the company.

> Also, would like to hear your thoughts on building a new system vs building on top of the many available open source medical systems. Thanks for asking. I'm sorry in advance that this reply is lengthy. I'll try to be succinct. Starting HospitalRun in 2014 was a very intentional, deeply-considered decision on our part, made after reviewing a wide spectrum of the available open source and commercial solutions for our network of developing world charitable hospitals at CURE International. We simply couldn't find a solution that we felt could both meet our requirements and be successfully deployed across our network. So without saying anything for or against other health system projects from the past or present, I'll say that the following were the driving factors for the decision to build HospitalRun. 1) Taking usability very seriously. For us, that doesn't just mean UX and clinical usability or even just administrative usability (since there's a lot more than just the doctors we're trying to serve). It also means easy to setup, easy to administer, and (and we're definitely not there yet) easy to contribute code. A developer is already doing A TON for a project like this by absorbing a totally unfamiliar set of business requirements. We want to make the experience of contributing to HospitalRun delightful. Like I said, that's aspirational - not reality yet... but that's part of what we think "1.0" looks like. 2) Architecture choices: we're committed to modern, cloud…

Conceptually, I think everyone at the U.S. Digital Service would be comfortable with working on a remote team. Many of us have done it, and since we're scattered across agencies, the group itself operates in a fairly distributed fashion on a day-to-day basis. Remote work does work at 18F, where they are often shipping projects that are self-contained and executed in-house. It's also a lot easier to build a remote-friendly culture if you start on day one, which 18F did. It's really just about the nature of the work we do, embedded on these agency projects, that necessitates being in D.C. The role of USDS HQ is simply different -- we're often grafted onto existing 'culture' elsewhere (I work on a floor with more than a hundred of product and engineering folks who were here years before we arrived), and are then tasked with helping to advise/fix/transform those projects as quickly and effectively as possible. (I'd also read https://blog.newrelic.com/2014/03/26/depth-look-team-saved-healthcare-… which was a precursor effort.) If you're interested in serving in the U.S. Digital Service but are in a position to be only able to work remotely, 18F is a pretty great option.

Is it though? Depends if you're triggering it six times a year or six times a day. Some companies pride themselves on how often they deploy code to production [1]. And whether your SPA is something like Google Docs where a user could plausibly have the same document open for a week or more. [1] https://blog.newrelic.com/technology/data-culture-survey-results-faste…

as has NewRelic. https://blog.newrelic.com/2017/09/13/distributed-tracing-opentracing/

This is called out of band GC. We've been doing it for years in Ruby with Unicorn https://blog.newrelic.com/2013/05/28/unicorn-rawk-kick-gc-out-of-the-b… However when the ruby community moved to Puma which is based on both processes and threads it was needed less. Not that this is rocket science (it's still far behind the JVM and .NET), I assume a hybrid process/thread model is something that hadn't reached a critical mass in the Python/Django/Flask/Bottle community?

Hmm, it looks like they have changed their pricing strategy. When I first signed up it was no strings attached free as a loss-leader to move you towards using their application monitoring products. https://blog.newrelic.com/2011/11/08/server-monitoring-is-here/ So far I appear to still be grandfathered into the the free server plan? Anyways, I guess you can disregard my original comment.

"The time for Dockers and containers isn't quite today, but it's very close." Hmmm ... tell that to AirBnb (http://nerds.airbnb.com/future-app-deployment/), New Relic (https://blog.newrelic.com/2014/08/12/docker-centurion/ ) and Spotify (https://blog.docker.com/2014/06/dockercon-video-docket-at-spotify-by-r… It is a young technology, but moving quickly. Just 10 years ago, YouTube wasn't owned by Google yet and we didn't have the first iPhone. Hell, 17 years ago VMware (arguably the king in the virtual machine software market) was founded. If it was a kid, it wouldn't have graduated from high school yet!

If you write into support at New Relic (or email/call a sales rep that you have already worked with), we can get an account exec to chat with you about pricing more appropriate to your situation. We are aware that in a world of autoscaling and micropriced micronodes, a different pricing model is likely to be more appropriate. You can see the first shot at a revision like this with the pricing restructure on heroku that we announced last december: http://blog.newrelic.com/2013/12/04/new-relic-announces-new-pricing-he… Your complaint is totally reasonable and NR is hoping to address it soon!

SQLite is the Rails default, in fact. In October 2013, NewRelic reported that 53% of their customers are using PostgreSQL: http://blog.newrelic.com/2013/10/10/infographic-state-stack-ruby-editi… In July 2014, Planet Argon's Rails survey showed a surge in preference for PostgreSQL since 2012: http://rails-hosting.com/Results/2014/index.html#Database Neither captures the distribution of usage from small- to large-scale apps, but it does look like the community has already moved both in mindshare and number of production deployments. I'd wager that Heroku's PostgreSQL default is responsible for much of that.

Your server would have handled it fine if your WordPress install had some basic performance tuning. Read http://browserdiet.com/ or http://blog.newrelic.com/2013/02/07/web-performance-optimization-autom…

Interesting to read the (linked) article on how they actually built the support: http://blog.newrelic.com/2013/10/22/new-relic-node-js-apps/ Since node's native support won't land until 0.12, does anyone know what the downsides of the polyfill are? Is there a much larger performance hit?

May be Appfog might work on enabling ssh because on local installs of cloudfoundry, you can run ssh commands. http://blog.newrelic.com/2012/01/26/removing-the-operating-system-barr… https://groups.google.com/a/cloudfoundry.org/d/topic/bosh-users/sdxVSi…

original source: http://blog.newrelic.com/2012/05/18/infographic-top-performing-payment… and direct link to the infographic: http://blog.newrelic.com/wp-content/uploads/PaymentGateway-Infographic…

There's also New Relic's end user monitoring. http://blog.newrelic.com/2011/05/17/how-rum-works/

I just posted the latest State of the Stack for Ruby. http://blog.newrelic.com/2011/09/28/state-of-the-stack-a-ruby-on-rails… It has: - A breakdown of ruby versions - A chart showing the changes to ruby versions deployed since Rails 3 came out - A breakdown of rails versions - A breakdown of ruby dispatchers - The top 50 gems and top 50 plugins

Creator of ack here. The three biggest reasons to use grepalikes is not necessarily the time to execute the search, but 1) The reduced amount of typing. It's much faster to type "ack foo --ruby" than it is to type "find . -name '* .rb' | xargs grep foo" 2) Better filetype matching, because ack and ag check things beyond just file extensions. ack's --ruby flag checks for *.rb and Rakefile and "ruby" appearing in the shebang line, for example. 3) More features that grep doesn't include, like better highlighting and grouping, or full Perl regular expressions (in ack) and a ton of other features. Here's a command line to find all the header files in your C source. It takes advantage of the ability to use Perl's regular expressions to specify output: ack --cc '#include <(.+?)>' -H --output='$1' | sort -u Here's an article I wrote a while ago on comparing the features of ack and ag. https://blog.newrelic.com/2015/01/28/grep-ack-ag/ Even though I created ack, I don't care which tool you use, so long as it suits your needs and makes you happy, but if all you're using your grep/ack/ag for is "grep -R function_name ." then you're only scratching the surface of what the tools can do for you.

If anyone wants to help fix the problem, I suggest the newly formed USDS. There are a lot of ex-Google people involved trying to help clean up and secure IT infrastructure in the Government. I spoke with someone who did a short stint with them and it sounds like they're actually being empowered to fix things. https://www.whitehouse.gov/digital/united-states-digital-service/story Mike Dickerson gave a really good in-depth talk at Google about his work cleaning up the healthcare.gov project. The Time article lacks many of the technical details but is still pretty good. Sorry, all I can find is a link to the PDF. https://blog.newrelic.com/wp-content/uploads/80893.pdf From talking to people who've worked in the USDS, the problem doesn't appear to be lack of capable people, or lack of funds. The problem seems to be in the structure of how projects are bid and executed. The bad news is the problem is universal. The good news it's fixable ... it's just going to take a lot of work by a lot of smart and determined people. Sign up and go fix it.

Related, I was recently in the depths of understanding Kafka from the consumer side, specifically a very busy topic with many partitions. Some blog posts I enjoyed: 1. https://blog.cloudera.com/scalability-of-kafka-messaging-using-consume… 2. http://www.vinsguru.com/kafka-scaling-consumers-out-for-a-consumer-gro… 3. https://medium.com/@jhansireddy007/how-to-parallelise-kafka-consumers-… 4. https://medium.com/@durgaswaroop/a-practical-introduction-to-kafka-sto… 5. https://blog.newrelic.com/engineering/effective-strategies-kafka-topic… And a fun one from Microsoft: https://azure.microsoft.com/en-ca/blog/processing-trillions-of-events-…

"If wanting to know up front if this is designed for the future or the past is an edge case, it's a pretty crowded edge. Python 3 was released eight years ago" good point: a quick search reveals that Py2.x is still in a lot of legacy code (dependencies -- the big one), so I always check first: - https://python3wos.appspot.com/ - http://stackoverflow.com/questions/30751668/python-2-vs-python-3-2015-… - http://hiltmon.com/blog/2014/01/04/python-its-a-trap/ - https://blog.newrelic.com/2014/01/21/python-3-adoption-web-apps/ - http://www.randalolson.com/2015/01/30/python-usage-survey-2014/