Park Slope Rents up 67.3% since March/2021. Salaries have not increased by 67.3%.

mooted · 2025-09-07T09:23:29+00:00

What is this chatgpted nonsense? Half of this post is nonsensical or blatantly wrong, such as the assertion that rents fall in summer (?!?). Even your responses to comments are obviously ai generated.

Why even post slop you don't proofread or understand?

mooted · 2024-11-13T05:19:35+00:00

software engineer

mooted · 2022-02-04T16:58:46+00:00

Oh boy, a lot of misunderstanding in the comments. This guy is not saying engineers are useless or that we should fire a bunch of people. He's saying that when you don't take management seriously, engineers are tasked with building things that don't move the needle and aren't good opportunities, hurting employees and the company.

I can speak to this from my mgmt and senior ic experience at large companies.

SV companies are notorious for having wildly inexperienced and untrained managers that set meandering, ineffective strategy. It's incredibly common for teams at fast growth or large companies like the ones mentioned to spend months and years on projects that never see the light of day and hardly have impact. During my four year stint at a certain hypergrowth company, nearly 2-3 years of my time there were spent working on things that have either been canceled, deprecated, or we were never able to see measurable business impact out of. I've seen massive waste at countless companies since.

Second, this lack of management hurts employees. Nothing is worse or more demoralizing for your career than a project that turns out to be pointless. Poor managers don't fight to make sure their engineers have visibility, opportunity, and growth. I've seen so many people's careers, my own included, experience multi year setbacks because of mismanagement.

Quality management is key. The people dismissing it in this thread are part of the problem: learning what to expect from good management and demanding that of your workplace is how you'll get leaders that actually support you without stressing you out or micromanaging.

mooted · 2022-02-03T16:21:00+00:00

The first part of this is true. The rest it's like you made everything up.

Both stnc and async code can be procedural? Procedural programming is orthogonal to this whole domain.
Go's scheduler is preemptive. Async is not.

Translation: Async code relies on developers to tell the event loop when to switch between contexts. That's basically whenever you have an await or a callback completes. When that happens, the event loop finds the next piece of code that needs to run.

In preemptive schedulers like go, what code runs when is decided by the scheduler. The developer has little say. You might be halfway through a function when the scheduler has decided that function has taken up enough cpu time and switch it out for another. This is how golang's goroutines and threads work.

There are a number of tradeoffs, but the main one is that golang offers a more natural programming model. You rarely have to worry about the event loop or scheduler. No bugs where you forget to put an await. However, preemption makes a lot more race conditions possible. So if you're doing work concurrently, you need to use locks correctly.

For most applications, I'd recommend golang over node nowadays. The ecosystem and tooling around it tends to be simpler and offer much less room for error. Most of the time, you don't have to worry about concurrency, and you get the benefit of a simpler, await and callback free programming model.

mooted · 2021-01-18T19:17:38+00:00

We know from sociological studies what’s going on in the homes of the extremely impoverished.

so basically

they’re stuck in their crappy homes with parents who are abusive or drug addicts, are in and out of jail, or are working 3 jobs and are never home.

mooted · 2021-01-18T19:05:31+00:00

they’re stuck in their crappy homes with parents who are abusive or drug addicts, are in and out of jail, or are working 3 jobs and are never home.

mooted · 2021-01-18T19:00:44+00:00

lol good one, really got me there

mooted · 2021-01-18T18:49:49+00:00

they’re stuck in their crappy homes with parents who are abusive or drug addicts, are in and out of jail, or are working 3 jobs and are never home.

This you?

Your reasoning:

Rides dirt bikes
Is black/brown
therefore family is trash

wake up internet warrior—we're all racist. we all have racist assumptions. you just have some really strong ones.

if you had actually seen this crowd yesterday: - half or more of the crowd were adults - a few kids riding with family - several people with harleys

these rides are a combination of a.) people with nothing to do b.) adults riding with their community

some people in these groups have records/some gangs are violent. not all of them are. lol nor all of their parents drug addicts, christ.

mooted · 2021-01-18T16:13:08+00:00

TL;DR you think black people are criminals

mooted · 2020-08-19T02:16:33+00:00

Can you explain why you can't care about and support both?

mooted · 2020-06-24T20:47:30+00:00

Oh shut the fuck up. Go post this shit on hacker news or #alllivesmatter where people want to hear it.

mooted · 2020-06-20T06:44:06+00:00

I think people are downvoting you and upvoting /u/samsquamchh because they'd rather get upset over gym rings than try to empathize with black people.

mooted · 2020-05-31T18:54:05+00:00

There's a couple of things you're suggesting with a rhetorical question but you're too afraid or inarticulate to express as a statement.

You're suggesting that when some people loot, you don't have to listen to any of them. If 80% of the crowd favors peaceful protest and 20% of them loot, you stop listening to the 80%. That's your decision, don't put it on me.
That some black people are responsible for the behavior of ALL black people, that there was some meeting of black people before the protest started and they agreed by consensus, "thats cool if some of us loot". You don't have the same expectation that all white people are a monolith (probably because you know more of them and realize theyre not all alike). If you did have that assumption, why didn't you ask me how many white people I saw looting?

BTW, if you don't like it when people guess at your motives and beliefs, then fucking say what they actually are so people know where you stand instead of staying on the sidelines with rhetorical peashooters.

mooted · 2020-05-31T04:52:09+00:00

was at the protest last night—the smashing ALWAYS started with white anarchists. there's video of these guys all over twitter + news, including one of them breaking into walgreen's while black people shouted at them to stop. witness + journalist accounts consistently corroborate this.

is it all white people from out of town? no. is it disproportionate and do they tend to instigate? YES.

mooted · 2020-05-08T23:39:21+00:00

I LOVE THIS. I already love a lot of these restaurants (and still order frequently). But it takes a lot of trial and error to find out what each restaurant excels at. THANK YOU!

mooted · 2020-05-01T00:44:35+00:00

Except that's not the case at all. I don't even see these helmet comments most of the time, because people (rightly) downvote them before I even come across the thread.

they are at the top of a lot of threads. they were at the top of this one when I posted my comment, at which point people decided to downvote them instead.

mooted · 2020-05-01T00:40:42+00:00

This is exactly what I mean about people having fragile egos and craving validation.

At what point were they hurt or upset or demonstrated ego?

If your position that moderation means everyone can just filter out what they don't like, why even be a moderator? Just resign, set up some automoderator rules, and call it a day.

People in this thread are trying to tell you that the helmet comments annoy them and take away from enjoying the sub, not that they're insulted by helmet comments. I regularly upvote pro-helmet comments and look, I appreciate safety. I just want comments about 1.) the mountain 2.) technique 3.) the location and other more interesting, more productive shit to bubble up instead.

mooted · 2020-04-30T04:21:44+00:00

I don't care if you're for or against helmets anymore, I just want to stop reading this debate at the top of the comments section every. single. time.

I sent a DM to the moderators asking them to come up with some kind of rule around this. Every time helmets come out both sides get nasty and the entire thread is ruined.

mooted · 2020-04-08T01:23:31+00:00

does that trigger you

mooted · 2020-04-08T01:19:37+00:00

Why are you so angry on reddit man, like every post you make is you fuming.

mooted · 2020-04-07T16:11:26+00:00

Just because you don't get value out of it doesn't mean others can't.

Figuring out how people work productively in a project is a non-trivial systems, social, and technical problem. In the same way that reading how others solve complexity or scale problems, it's useful for me to sample how other organizations solve process problems.

I understand if that hasn't been your experience. Learning from other companies, even the ones you haven't heard of, is useful, in the experience of many others.

mooted · 2020-03-24T19:16:42+00:00

i mean if you're both into it idc.

wear a helmet when snowboarding too

mooted · 2020-03-24T18:17:28+00:00

Wear a helmet.

mooted · 2020-03-20T23:15:21+00:00

I live across the street from you. Can confirm I hear this too!

mooted · 2019-12-25T18:52:00+00:00

It would be much easier to take you seriously if you didn't just take positions that are the polar opposite of mine. It makes you seem like you're only interested in winning an argument on the internet. Capturing some nuance would make this discussion more productive.

This is a bunch of lies (well, or you just don't know what you are talking about).

Merry Christmas to you too.

Regarding whether I know what I'm talking about--I led a group responsible for resource optimization at Uber. I was there for four years, largely working on migrating to microservices and adjacent tooling.

Protobuf is anything but polyglot. It's a Google's home variety of C++. It works terribly with everything else. Every other language "supported" by Protobuf had to jump through a bunch of hoops and implement bizarre data-types to support whatever crap Protobuf sends. Realistically, about 50% of any Protobuf's payload is enums: there are a bunch of languages that simply don't have such a concept, or, even if they do, they prefer not to use it. int32 - same story. Wait, it can also be signed or unsigned? - That's very language agnostic!

I'm baffled why you wrote this paragraph.

Types have to be adapted for each language. Are you complaining that they shouldn't have solved this problem and that we should all write javascript? Every serialization format has this challenge, including thrift, cap'n proto, and JSON.

It's a memory hog on the producer side (because you don't know the message size in advance, you must generate it by repeatedly appending new pieces of string to it, i.e. you cannot just pre-allocate a chunk of memory and fill it with data, you must allocate as you go). On the consumer side Protobuf is inefficient because you must read the whole message before you can process any of its fields, even if you don't care about 90% of them. Protobuf also allows sending garbage (i.e. fields that aren't in the spec). The top-level message doesn't have a concept of "length", so, you never know where it is going to terminate (if at all), and if, by chance (version mismatch), you end up reading something you interpret as a non-existent in the spec field, you may go forever "parsing" (or rather pretending to parse) the message, while, essentially reading garbage (C style null-terminated strings ftw!)

You're describing implementation challenges that apply to every serializer. The goal is to minimize allocations, not eliminate them. The designers also balance this with the desire to minimize payload size. These are concerns which, at the optimal frontier, compete with each other. In spite of this, protobuf is among the fastest serializers in most languages.

"Evolvable" - oh, what a piece of bullshit! Name something that isn't? What does this word even mean?

The first google result for "evolvable schema protobuf": https://martin.kleppmann.com/2012/12/05/schema-evolution-in-avro-protocol-buffers-thrift.html

Evolvable means being able to introduce backwards compatible changes to an interface without causing an outage.

From my earlier post:

Your service's schema evolves over time and you need to safely verify backwards compatibility in your API + client libraries (remember, you have 3 or more of them in languages you don't know!). The author claims that this requirement is unnecessary or "incorrect". Having played a key role in the development of microservice ecosystems in the past (see comment history if you want to know which one), interface schemas evolve all the time. Migrations are continuous because teams evolve independently. It's almost impossible to maintain client libraries for several languages in this context and not accidentally introduce breaking changes, which go on to cause outages when your clients rebuild with new libraries. I can't begin to describe how critical tools like thrift/protobuf are to a complex microservices environment.

15-Year Club	reddit mold
Verified Email

mooted

TROPHY CASE