Little bit of everything!

Avid Swiftie (come join us at !taylorswift@poptalk.scrubbles.tech )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 40 Posts
  • 1.68K Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle





  • Exactly. Even Meta and their thousands of lawyers would immediately say this. How does it harm people? Prove it does. Why are they singled out? They’re just showing content they think is relevant, and I’m guessing they honestly are. It’s that political groups take advantage of that, and make slop that enrages and inflames. But Meta would just say “you can’t punish us for trying to make our platform successful”. A mess all around











  • As someone who works in corporate America this is 10000% true. Giant corporations are hugely bloated, inefficient, slow, and stupid. I honestly can’t believe they are somehow the best way to do things in groups of people. I have never had less work to do than working in a huge corporation.

    It’s no surprise that indie games can compete with them. Working in startups compared to huge corporations, I did more code and we got more done in shorter amounts of time vs big corps. There’s no red tape, there’s no committees or directors or people you have to please. There’s no political games, you just do your work. As simple as that. You come in, you code for 7-8 hours, you push your feature, and you go home.

    In a megacorp you come in, you get 5 minutes for coffee before 3 people are pinging you on slack for some stupid downstream thing they didn’t read the manual on or was never documented, and then you have 5 hours of meetings, lunch, 2 hours of ad hoc meetings, and then Shirley has to swing by to ask you to take another HR training. So you get maybe 20 minutes of coding done in a day.

    For you engineers who have never coded in a megacorp - As an example, most megacorps have an ID service (usually named after a comic book character). This is usually a real service deployed somewhere that nobody maintains anymore, but it’s where you get your… IDs from. Really wrap your head around that. It’s a microservice who is in charge of returning Guid.NewGuid(). Then they get pulled into meetings because the ID service doesn’t support this or that, they never thought of this case or that case, how can we upgrade off the old ID service to the new one. In a startup, you’re calling Guid.NewGuid()