moreaccountspls

There's a "Curb Your Enthusiasm" episode where Larry David's character donates to a museum with his name on the donation. There's no self deception for him; he wants to do something good AND he wants the credit. And that's totally fine! The character is self aware enough to know that part of his motivation is selfish.

My point is that by not acknowledging the selfish part of "wanting the credit", the author comes off as not self aware [or disingenuous, but let's give them the benefit of the doubt]. That's what I meant by cheapening it for them.

It lessens it for the author because they're looking for validation from someone in some type of way, the same way the breakfast people do. If you're content being someone that needs validation from other people for your actions, then sure, it doesn't lessen it for them.

It's a bit sad that you've taken a wonderful, altruistic act and cheapened it by feeling the need to broadcast it on the internet :(

No, it's not relevant. There's no considering being done, the feature is being shipped. Please stop with the Rust spam.

Nah, there's something unique about Rust zealots in this respect. nicoburns comment is completely off topic, and it's extremely obnoxious to see this kind of thing over and over again from the Rust community. And I even like the language!

That's unfortunate. Try a different dermatologist? I've gone to flatiron dermatology in the past, and they're solid.

I wish I could upvote this a thousand times. At the end of the day, it's all ego driven development. Nobody wants to think that their job has already been solved, and what's left is mundane and boring [engineering wise]. And so the business ends up with using a distributed log to handle a data set that could fit on a big thumb drive.

Yes, but there at least is some genuine innovation going on. The backend frameworks are just churn for solving the same boring and lucrative business problems in new, fashionable ways.

Obviously you should do what you feel comfortable with, but now is a good time to go the doctor and get that checked out. The numbers are pretty low and stable for the moment. And FWIW, I had surgery last week so I'm not giving advice that I wouldn't follow myself.

Alright, I'll bite. Why do you think not breaking users programs is abandoning quality?

I very well could be wrong, but that's almost completely besides the real point [as well the self diagnosis regarding ADHD].

The amount of anxiety you're experiencing in your day to day life is grossly abnormal. I would suggest not waiting another day to start seeking out the help [therapy or working with a psychiatrist] you deserve. I also you suggest you research hallucinogenic medications as something to possibly relieve your existential anxiety: https://www.hopkinsmedicine.org/news/media/releases/hallucin...

The lexer shouldn't have to deal with that sort of stuff.

The problem with that is that the entire python ecosystem had to deal with that instead...

I'm going way past rant territory at this point, but there's a reason that Microsoft and Amazon are worth a trillion dollars a piece, and it's not because of beautiful and elegant APIs.

So what? In the history of Python, there was literally 0 bugs caused by print being a statement. Breaking backwards compatibility for shit like that is amateur hour.

edit: And just to be clear, I'm fine with making print a function for all new code. There were ways that the python community could have accomplished that [and the unicode switch] without breaking the entire language.

It sounds like you're experiencing panic attacks.

Writing some optional, non-essential piece != rewriting a piece that will require taking rust as a dependency for the rest of time.

The kernel folks just did a lot of work to remove the strict dependency on GCC. To think any of the big players [Red Hat et al] want to turn around and make their shining star dependent on a language that's been 1.0 for less than 5 years is just not realistic.

Right, which is why it's a poor choice for the kernel at this time.

For the Linux kernel? Absolutely. Rust is way too unstable right now for such an important piece of software. Give it 20 years and a standard, then we can talk.

I wouldn't be too worried about it. The kernel people aren't going to take a dependency on something that isn't standardized and doesn't have a spec.

not putting your engineering due diligence into delivering a product to the customer.

Yes. This is exactly what this person should do. Stop worrying about arbitrary rules and just deliver the damn product already. A hacky, shitty, unfinished product in your customer's hands that can be iterated on beats one that never got shipped at all every day of the week.

Sure. My point wasn't really whether to write unit tests or not. It's more, do what works for you / your team to enable you to ship consistently. For the OP, spending all of their time writing tests clearly isn't working for them if they haven't shipped at all.

I don't understand your point. We're specifically talking about a one person company.

I'm no fan of Amazon, but it's the third most valuable company on the planet. Whatever they're doing is obviously working for them, even if I personally wouldn't want to work there.

Well, then stop! Delete all the tests right now and do it however you want to do it.

The thing about testing that never really gets talked about it is, what's the penalty for regressions? What's the consequences if you ship a bug so bad the whole system stops working?

Well, if you're building a thing that's doing hundreds of millions in revenue, that might be a big deal. But you? You're a team of one! You rollback that bad deploy and basically no one cares!

Your customers certainly don't care if you ship bugs. If it was something important enough where they REALLY cared, they wouldn't be using a company of one person.

So, go for it. Dismiss tests until you get to a point where you fear deploying because of the consequences. Then add the bare minimum of e2e tests you need to get rid of that fear, and keep shipping.

It doesn't work like that though. You can't ignore the diminishing value of money.

It's never required: https://stedolan.github.io/jq/manual/#Streaming

You think everyone building tools like k8s, terraform, etc. are fools? That's a pretty myopic worldview.

There's a difference between operating the database [SRE type job] vs consuming a database [developer]. They're both very valuable skills, but learning the basics of SQL [i.e. being a consumer] is a no brainer. The skills will serve you well for the rest of your career. It's not something that changes every few years like frontend frameworks do.

This is my favorite learning material for ANY programming related skill ever: https://use-the-index-luke.com/, and it's all about SQL queries.

Sure, and if the moon was made of cheese, it would still be a sphere lighting up the night sky.

The fact that the go designers prioritize things like statically compiled binaries is the whole magic of Go in the first place. The language is whatever, it's fine, it's cool. But like the article says, the magic is in its holistic attitude towards process, tooling, and distribution.

Or, you know, just return Object from a couple of methods. It's not the end of the world.

You can use `go generate` with the AST package and get the same thing.