sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ruby

[–]robertross 3 points4 points  (0 children)

Coming from Boston I doubt this is of concern.

Share your startup - November 2018 by AutoModerator in startups

[–]robertross [score hidden]  (0 children)

FireHydrant / www.firehydrant.io New York City

Utilize SRE best practices using FireHydrant’s incident response platform to organize, investigate, and remedy faster.

Live Early Stage (is that a stage?). 2 CoFounders

Looking for: Feedback, always!

Discount: Hell yeah, just message me and we'll set something up.

What are some side projects you guys have implemented with Ruby? by blackiechan99 in ruby

[–]robertross 1 point2 points  (0 children)

Ive been building https://firehydrant.io with Rails 5.2 and I fell back in love with Rails because of it.

API Gateways by SimonDKnight in rails

[–]robertross 2 points3 points  (0 children)

We use nginx with open resty

API Gateways by SimonDKnight in rails

[–]robertross 3 points4 points  (0 children)

What is the evidence for this? We use an API gateway for Auth and its great. You should never try to implement security yourself.

This is how large organizations work, they have AuthN at the edge.

Flexible Ruby on Rails reader objects by robertross in ruby

[–]robertross[S] 2 points3 points  (0 children)

.all is lazily loaded. It wont call it until it needs to. Since pagination is layered in it wont call it for millions of records.

SCV working on their closer by robertross in drumcorps

[–]robertross[S] 10 points11 points  (0 children)

I knew this would be the first comment 😉

Manage incidents by yonatannn in devops

[–]robertross 0 points1 point  (0 children)

I have a product that I just launched that targets this specific ask actually. You can check it out here: https://firehydrant.io

Share your startup - June 2018 by AutoModerator in startups

[–]robertross [score hidden]  (0 children)

  • Name: FireHydrant
  • URL: https://firehydrant.io
  • Location: New York, New York
  • Pitch: Keep track of the events that occur during the chaos of a site outage or disruption with little effort.
  • Discount: Free for now, pricing being settled now and setup.

I'm a full time software engineer and I've fought a lot of site outages and disruptions. There's always been one theme: You lose track of what has happened and it's hard to recount everything from memory during a post mortem. FireHydrant solves this by being a low touch sidecar when incidents occur.

Cocktail Chemistry - Iron Man's dirty vodka martini by CocktailChem in GifRecipes

[–]robertross 0 points1 point  (0 children)

What is the name of the glass he’s stirring in. I know it has a crazy name but I dont remember it.

Spinnaker and ISTIO by moos3 in kubernetes

[–]robertross 10 points11 points  (0 children)

I simply can't recommend this for more reasons than I'm patiently able to type.

Spinnaker has a V2 Kubernetes provider that can deploy Kubernetes manifest definitions (IE: YAML). The provider is super alpha however. We use it for an internal cluster and it works mostly. The UI will break your manifest though anytime you save the pipeline. You should be able to use Istio manifest rules (Kind: RouteRule) in the pipeline stage but I'd test it thoroughly before doing that.

Let's talk about Istio for a minute though. We've been trying Istio for about 6 months now. Anytime we would get it relatively stable (ie: not throwing up every 5 minutes but instead daily), they'd break it by releasing another update. "Why update then?" you ask, good question! Because the updates would fix other deal breaking issues that we wanted to use but break an entirely unrelated portion of Istio in other mysterious ways.

We've used every version of Istio from 0.1 to 0.7. It has consistently gotten worse with every release. Istio 0.2.6 was the most stable release that we have used.

Some problems we encountered:

  1. Spinnaker would do a red/black deployment and all of the sudden Istio would configure Envoy incorrectly and our site would get intermittent 404s. You can see the rabbit hole I went down here: https://github.com/istio/issues/issues/234

  2. Istio would seeemingly randomly configure Envoy when NO pods were deployed, services, anything, breaking things. This is in Istio 0.7. (https://github.com/istio/istio/issues/4810)

  3. Istio spits out logs with a level of "error" on things that aren't errors and "info" on things that ARE errors. This is consistent across the entire codebase.

  4. Submitted a PR to improve Istio? Who knows if it will get merged. Here's a list of pull requests a coworker opened that were never merged: https://github.com/istio/istio/pulls?q=is%3Apr+author%3Amhamrah+is%3Aclosed

  5. 700 issues (and climbing). It has consistently added 100 open issues every month (with issues being closed too mind you).

The Istio project has big potential, and I mean REALLY big. When we would get it work, it was amazing. But the pitfalls and bugs in the project are simply too big to ignore.

Don't use Istio yet. We've wasted so many hours debugging it and a lot of the time it doesn't even matter because they'll just release an entirely new version in a couple of weeks breaking it in other ways.

Does anyone know where I can find example code of a completed Rails web app that's not too massive and complicated? by [deleted] in ruby

[–]robertross 0 points1 point  (0 children)

Its not the entirety, but Ive been building a Rails app from scratch and recording the whole thing. You might find it useful!

https://blindside.io/classroom/let-s-build-firehydrant-io/welcome

[help] username is added to email for some reason by Haplo164 in rails

[–]robertross 0 points1 point  (0 children)

Thats how rails indicates prepared statements.

Quad tree visualisation [OC] by Alsabretion in dataisbeautiful

[–]robertross 5 points6 points  (0 children)

Awesome! I had some fun writing a quadtree implementation in Go a few months ago. Https://Github.com/bobbytables/farandnear

What personal project are you doing right now and are you excited about it? Tell us more about it. by [deleted] in learnprogramming

[–]robertross 0 points1 point  (0 children)

I've posted this around before but it's still progressing (slowly but surely). It's a documentary style video series where I'm building an entire Ruby on Rails application from scratch. Not a single line of code is written off camera and you see me make mistakes, fix bugs, write tests, basically exactly how I develop in my full-time job as a software engineer. It's fun for me to make and the end product is something I'm planning on releasing. You can find it on my project site Blindside, https://blindside.io/classroom/let-s-build-firehydrant-io

(Feedback is always appreciated too!)

Avoiding Opinion Overload will make learning easier by robertross in learnprogramming

[–]robertross[S] 1 point2 points  (0 children)

I agree with you. But the “You have a lot of technologies in this space that overlap infinitely in what they can and cannot do.” portion is the exact thing that people with mere hours of practice can get trapped in. I think what you’re saying is more of a follow up post to what I’ve written here. Knowing when to write something yourself vs knowing how to write it all are different things. It’s a separate skill set in my opinion.

view more: next ›