Raygun Blog

Disclosure: I'm the CEO of Raygun (https://raygun.com). Raygun provides Crash Reporting & Real User Monitoring. Across both mobile, backend and desktop (and all mobile, including Xamarin stacks). Love to have you check it out. We've been picking up a bunch of customers who have been getting nervous with Twitter being in a bad shape and worrying about Fabric previously.

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

Raygun | Seattle, US & Wellington, NZ | Engineering & Sales | Permanent Full time | Onsite ---------------------------- ---------------------------- ---------------------------- ------------------- Raygun gives developers the power to create perfect software experiences on a global scale. ---------------------------- ---------------------------- ---------------------------- ------------------- Https://raygun.com/careers Sales Roles | Seattle, US Sales Development Rep Account Executive VP of Sales Customer Success Manager Get in on the ground floor of an already successful SaaS business! How? Raygun (https://raygun.com) is setting up a sales office in Seattle – it’s first sales office globally. The Raygun Platform is already in use with thousands of customers in more than 100 countries. We’re a high growth, but profitable, business. We achieved this with a great product coupled with great marketing. Simply put, you’ll be helping find new leads for a product that has proven value to software development teams in a rapidly growing market. Engineering Roles | Wellington, NZ Software Engineer - We are always on the look out for awesome software engineers You love coding to the brink of obsession! The code you write is clear, easy to maintain and unit test. You care about the user and you get a kick out of building features they love using. You will excel in a collaborative and agile environment where we deploy continuously, measure everything and take…

Raygun | Developer Evangelist | San Francisco | https://raygun.com | Negotiable As a full time Raygun Developer Evangelist you'll be responsible for spreading the word about Raygun to developers around the world, online and in person. Raygun is growing FAST and needs social coders to help us reach and enable even more developers to build better software. A successful Developer Evangelist has equally strong technical and people skills. You love to code, but you love to talk to people about code just as much. The ideal candidate is a software developer interested to share their knowledge and passion with other developers. Does this sound like you? * You build apps and code in your spare time just for fun. * You love teaching others about new things. * You blog about your technical escapades and discoveries. * You participate in online communities like Twitter, Stack Overflow and Hacker News. * You attend hackathons, conferences and meetups to build new things and network with other people. * You keep up with new technologies, trying many of them out for yourself. * You enjoy giving technical talks and presentations. If you regularly do many of these activities, you'll enjoy being a Developer Evangelist! Candidates can apply for this exciting role at - https://raygun.workable.com/jobs/246682 https://raygun.com/careers

Looks like a top notch implementation that's had some serious effort put into it for solving their unique pain points around deploys and monitoring. My colleagues and I at Raygun (https://raygun.io) have created an error tracking service that from an overview ticks the boxes that Haystack supports, and a whole bunch more besides for dev teams who don't happen to be GitHub :) Tools like these become pretty invaluable when releasing code into the wild, and aside from lifecycle benefits like greatly reducing the cost of the maintenance phase, an error tracker can also alert and hand the data needed to fix the bug right to the person who can, greatly increasing dev sanity (no more relying on support ticket ping pong, and removes the onus on the end user to report the bug). Also, surfacing the attack vectors and the frequency of which adversaries attack code exposed to the web is rather eye opening.

I love the idea of a formal hanseikai (反省会). Perhaps a Museum of Software Accidents is called for? https://raygun.com/blog/costly-software-errors-history/

After watching that talk, I would have loved somebody in the audience to point out instance like this https://raygun.com/blog/10-costly-software-errors-history/ and ask for Hickey's comments. Needless to say I really don't agree with that list, as history shows the inconsistency, typos, lack basic units and the ability to express them in a computation etc., have been more catastrophic than he believes them to be. And these issues cannot really be fixed without a proper type system, that will not allow stuff like that to get into production. And a good type system cannot be optional, e.g. clojure's spec, There are number of studies that show that will power, is not enough, there needs to be and environment - a type system - that helps to avoid and catch mistakes.

Thank you for sharing your initial research. Too many AskHN drop a question without hint what the user already looked at. https://raygun.com and https://www.honeybadger.io/ seem to be US, too. https://appsignal.com/ is based in Amsterdam.

>After watching that talk, I would have loved somebody in the audience to point out instance like this https://raygun.com/blog/10-costly-software-errors-history/ and ask for Hickey's comments. Needless to say I really don't agree with that list, as history shows the inconsistency, typos, lack basic units and the ability to express them in a computation etc., have been more catastrophic than he believes them to be. From the list you cite, only three of 10 errors are caused by "typos", "lack of basic units" and type errors. And this is just a particular list. Recalling Rich Hickey list, the things that cause more problem in code, from worst to less damaging: Domain Complexity Misconception 10x Place Oriented Programming Weak support for information Brittleness/Coupling Language model complexity Parochialism/context weak support for Names Distribution Resource utilization Runtime intangibility Libraries Concurrency 10x Inconsistency Typos I'm pretty sure that if we compile a list of real-life cases where the major reasons of failure according to Rich Hickey have caused trouble, the list of examples would be immense, compared to "typos".

Maybe not the space shuttle, but: NASA’s Mars Climate Orbiter; crashed or is now inoperable and orbiting the sun due to a bad numerical conversion. ESA’s Ariane 5 Flight 501; manual self destruct triggered after a 64bit number being truncated into 16bits caused faults to be thrown. https://raygun.com/blog/costly-software-errors-history/# I don’t think we should go back to manual operation (as the default, but should be overridable). Instead we should be using stricter compilers, and better unit, integration tests, and fuzz testing to test as many edge conditions as possible.

Thanks for the enlightenment. Did you not consider going for adoption by regular Mozilla users, and only then try expanding to the wide open internet? I have the feeling that by trying to tackle everyone at once you ran into brand recognition problems. For reference, I pulled this login screen from an image search on google: http://raygun.io/blog/2013/08/mozilla-persona-support/ The question must be asked: Does Persona have any chance of being used, in that context? This branding issue can be compensated by having the browser pull out a dedicated login interface, or by really leveraging the known Mozilla brand (accepting the negative aspect you presented, which is inescapable). Without compensation, it is indeed a lost cause.

I've been assembling a list of these lately for a book that I'm working on. (http://startingandsustaining.com) Some of the categories are fairly loose as some apps don't fit nicely into categorical buckets, but hopefully this is a helpful list. --Browser/Email Testing BrowserStack (http://www.browserstack.com) Litmus (http://litmus.com) --Bug/Issue Tracking BugHerd (http://bugherd.com) Lighthouse (http://lighthouseapp.com) Sifter (http://sifterapp.com) (Disclaimer: I built this.) --Planning & Project Management Sprintly (http://sprint.ly) Podio (https://podio.com) Flow (http://www.getflow.com) Interstate (http://interstateapp.com) Basecamp (http://basecamp.com) Apollo (http://www.apollohq.com) Pivotal (http://www.pivotaltracker.com) Asana (http://www.asana.com) Trello (https://trello.com) Blossom (https://www.blossom.io) Trajectory (https://www.apptrajectory.com) --Business & Traffic Analytics KissMetrics (http://kissmetrics.com) MixPanel (http://mixpanel.com) DigMyData (http://digmydata.com) --Continuous Integration / Code Quality Travis (https://travis-ci.org) Circle (http://circleci.com) CodeClimate (http://codeclimate.com) Sempaphore (https://semaphoreapp.com) --Dashboards Ducksboard (http://ducksboard.com) Geckoboard (http://www.geckoboard.com) Instrumental (https://instrumentalapp.com) --Error/Exception Handling Sentry (https://getsentry.com) Coalmine (https://www.getcoalmine.com) HoneyBadger (https://www.honeybadger.io) BugSnag…

https://www.androidpolice.com/2018/03/22/google-warning-developers-inc… https://www.reddit.com/r/androiddev/comments/868ie7/google_play_violat… https://docs.instabug.com/docs/gdpr https://stackify.com/about/gdpr/ https://raygun.com/gdpr https://www.loggly.com/about/privacy-policy/ https://www.sumologic.com/compliance/what-is-gdpr/ https://logsentinel.com/gdpr-practical-guide-developers/ https://help.papertrailapp.com/kb/how-it-works/security-compliance/ https://www.landoop.com/blog/2017/12/apache-kafka-gdpr-compliance/ https://www.splunk.com/en_us/solutions/solution-areas/security-and-fra… https://www.elastic.co/gdpr https://www.google.com/intl/en/cloud/security/gdpr/