RonSijm

There's a user made OpenAPI spec: https://github.com/MV-GH/lemmy_openapi_spec - You probably mean that one

I've had similar issues as you mentioned that the dev did fix - but yea, Typescript has less precision than Rust (the source) or the openapi spec. And the Typescript client is build for Lemmy-JS and not build an example for other language client libraries...

Though the OpenAPI Documents in C# and Java are based on reflection of the source itself, and Rust doesn't have Reflection like that... So it's probably difficult for them to add without manually maintaining the OpenAPI specs

About 4 ~ 12 a day, though roughly about 50 ~ 60 hours a week.

A 4 hour day would be if I have some problem that I know has a good implementation, but I just can't figure out how to do it. Then it's better to just stop and do something unrelated.

Though then once the problem is solved and all the puzzle pieces fall together - and I can just work on implementing it, and refactoring it into a good solution - I can continue working on it without caring about the time.

But I don't have a lot of days where at the end of the day I'm like "Yess, I'm finally done working, now I can start doing something fun!" - The working itself is already fun, so that creates a different "Working vs Not Working/Having Fun" dynamic

23 and Me are technically correct in that it’s customer behaviour that caused the issue.

Maybe I don't really understand what happened, but it sounds like 2 different things happened:

The hackers initially got access to around 14,000 accounts using previously compromised login credentials, but they then used a feature of 23andMe to gain access to almost half of the company’s user base, or about 7 million accounts

14k accounts were compromised due to poor passwords and password re-use -

And then they got access to 7 million accounts. Where did that 7 million account breach come from? Were those 7 million connections of the 14k or something? Because I don't think your connections can see many in-dept details

PaaS takes away your flexibility: [...] sometimes, you also want to use the compute to run cron jobs, run background jobs, or host a small service. With PaaS, you don’t have the flexibility to do so. [...]

I don't really agree with that. I'm using AWS for that, and for my "small cron jobs" I simply create a lambda for them. Then you can create a CRON rule in Event Bridge and schedule the lambda to start whenever you need

Maybe one of the 1800 disgruntled ex-unity employees that got laid off this week

Isn't that the same as modern languages? For example in ASPCore / C#, you can just register all your services with a lifetime scoped to the request, and then there's no shared state.

If you want there to be a shared state, you'd just have to register your services with a higher lifetime scope, like with a singleton scope

It is, for example, EFF has paid positions, and they're huge advocates of FoSS. "Opensource Advocacy" is not the job/job-title, but it's part of the job

Also there are companies that are FoSS at it's core - but get paid by clients for consultancy work for support and implementation of their FoSS. They have paid positions for advocacy for their software

Yea, there are more overpowered things to use with unlimited freecast, though the thing with the underpants glitch is that it takes an Action. So if you're trying to use this during combat, it's not that great.

Also with this method, killing anyone does not seem to get associated with you. So you can basically stealth kill anyone, and then walk back back in with your group and everyone around is still friendly

It's been in there since the beginning, I also would have assumed they would have patched it away by now.

There was a similar kinda bug with Markoheshkir, and they did patch that

From the screenshots it looks pretty easy to compile:

If they just ripped their entire git repos or something, and it's complete, it should be pretty easy to compile.

Edit: Compile instructions: https://pastebin.com/igt8BM4S

Yes. But are most managers too dumb to figure out that you can't program? Also yes.

He gave me one last tip. If I ever want to have a career in a management role, like CTO in the future, I must emphasize more on “taking credits” from the beginning of my career. He said being humble or modest is overrated and it would not do me any good for my career.

I don't really know if any of this is true, or what the context is. Maybe this is how it is in American Corporate culture, but it's not really how I experienced it.

If you're a beginner programmer, sure, you can brag about how cool your code is, and how much you've build. But if at some point you become a lead developer and you're still doing that, it seems kinda toxic.

As lead developer in the standup or reports I'd usually downplay what I did - like instead of saying "I build this cool new feature" - present it as "The backend team build this cool new feature". If someone else build something cool, I would specific say something like "Bob build a really cool feature"

I must emphasize more on “taking credits” from the beginning of my career. He said being humble or modest is overrated and it would not do me any good for my career.

A good Team Lead or CTO needs a good team, and the team usually appreciates it a lot more if you're spreading the credits around instead of taking them for yourself.

Besides that, a random developer in a big company is very unlikely to just become the CTO by not being humble. If you want to become a CTO, you either join a startup or start your own company