craigmcnamara

GraphQL seems like a great idea if you're a massive social media company looking for ways to empower devs to stamp out flavor of the week social media widgets without being tied to existing APIs. I'd bet most companies doing GraphQL are just doing uncacheable things that REST APIs could do fine.

I've written plenty of PHP, mostly out of necessity, but I find the language to be hideous. It's like they took only the worst parts of other languages and piled it all in to one full of `$` and `->` for no good reason. I've been a Ruby programmer for the last 15 years, but I spent 6 years writing lots of MFC flavored C++ and Java and I honestly can't fathom why given the opportunity to improve the language starting around PHP 5 they made the choices they did. It's like they saw good things other languages had and just did lazy imitations with the worst possible syntax. Composer is a half assed copy of Bundler and I still can't believe that a global php.ini is a thing.

Speak for yourself. In my shop we have CI/CD and we ship whenever we're ready to ship regardless of the day or time.

Microservices solve revenue problems at cloud hosting and CI companies.

Use 2FA in your password manager. 1Password supports it, I assume others also do.

What you said, but I'm considering carrying a rock now. Drivers seem to think I'm disposable for committing the crime of walking somewhere. Middle fingers are only so memorable, but that ding in the paint or a window might help them remember I have the right to not be hit in a crosswalk.

I find the GCP documentation to be lacking compared to AWS. Specifically while using GCP with Terraform I hit more frustrating nonsense error messages with little to no google hits or undocumented behavior around IAM config compared to my experience doing similar things on AWS.

Not the responsibility of the container. The host deals with those details.

Utica, NY. A historically significant city.

Fondly remembering the constant nightmare that was browser bugs and IE support from the mid 2000s to the mid 2010s.

Isn’t a zero ohm resistor just a jumper?

We should promote this patch to production ASAP

Sounds like you don’t write tests

The story you're telling sounds like a you guys problem, not a Ruby or Rails problem. I've been building and running Rails apps since 2007 and have not experienced what you've described.

My current app runs on AWS ECS. Upgrades are largely just updating my Dockerfile or merging a pull request from Dependabot. We have pagerduty and it only goes off when a 3rd party API is down, usually resolving itself.

On one hand she's a crook. On the other hand she scammed Ruper Murdoch, Kissinger, the DeVos family and a bunch of other ghouls that deserve to be robbed.

I guess in the end there we're more innocent victims than ghouls taken to the cleaners.

They did whatever could drive more dollars to deliver nothing contracts, but there was a particular hard on for getting XML in to anything. It was the solution to everything for a decade at least.

Ruby pays the bills and is nice to work with.

AFRL couldn't get enough XML in the 2000s.

On my previous team I used to think read only Friday was a good idea, but it was in fact a symptom of quality problems. My current team has a strong culture of testing and quality and we ship whenever the feature is ready.

And nothing of value was lost.

ViewComponent is years old, in large production deployments, and very stable.

I think it's good to prevent my test suite from becoming unintentionally stateful. People come and go from projects and you have to keep on top of security updates, so being strict about how things are done makes the project easier to manage in the long run.

You clean it up. I've cleaned up projects that we're total shit shows and the cleanup paid dividends when the time came to update or change that part of the code.

Even if a project has gone to seed, things rapidly get better when you start to do things the right way again.

This is a terrible attitude towards code you support for a number of years. It seems like you just get to dump on the next person, so I guess it works for you, but if one of my people sent a hatchet job in for code review they can expect to get an earful until they do it right.

This seems like a broken process to me.

No matter how free they make it to use, I just do not want a robot listening to me all time.

It wastes productive resources(power, hardware, compute time) on non-productive applications(Ponzi, digital beanie babies, gambling).

> Hey frens

Why talk like illiterate children all the time?

File that as "Cool thing that is an NFT, but doesn't need to be."

How is remote work a scam? Engineers don’t need a schmuck like you bothering them in person to do great work. Work from home gives everyone a private office, focus and quiet.