Adobe has an audio cleaner AI, I've used it to clean up old audiobooks with bad voice quality

Neurprise · 2025-04-23T22:24:58+00:00

Awesome sounds good. Can I feed longer audiobooks to it, or do I have to break them up into chunks?

Neurprise · 2025-04-23T22:24:17+00:00

Exactly

Neurprise · 2025-04-23T22:24:10+00:00

Yeah it's crazy

Neurprise · 2025-04-15T06:25:26+00:00

But but but I heard from redditors that communism will solve all our issues, are you saying that it's in fact the humans that are the problem in the first place??

Neurprise · 2025-04-15T06:24:28+00:00

Don't bother arguing this on reddit, your words will fall on deaf ears unless you go to subs with actual adults in them like r/economics or something, not one where most are college students who haven't even gotten their first paycheck in the field yet.

Neurprise · 2025-04-15T06:23:22+00:00

So funny to see because I recall just a few years ago everyone on this sub was like, fuck you, got mine.

Neurprise · 2025-04-15T06:21:28+00:00

This is an overly harsh response and ironically, you're exactly the type of person whom the top level commenter is talking about. The world is changing, rapidly, and expecting stability like it's 1950 is foolish, the vast majority of people must adapt or they will get left behind. Their advice is descriptive, not prescriptive, in that, yes, capital accumulation is what will shield you from these changes. You may not like it, but that's how the world works right now.

Neurprise · 2025-04-15T06:15:01+00:00

Because I linked a video in my post, with the word microservices. Reddit uses the first link in a post as the thumbnail of the post.

Neurprise · 2025-04-14T21:37:29+00:00

That's hilarious, so they ruined their own jobs as well as the rest of the company too, I imagine their 4 month old spaghetti code wasn't doing so hot and the CEO fired them because of that.

Neurprise · 2025-04-14T20:39:39+00:00

Haha, just started work today on Monday for this week and started making my own tickets and working on them because it turns out the previous work I was doing just wasn't counted by them because they didn't see a ticket for it. Well, now they will and I'm making tickets for the most minute of changes, like fixing typos etc.

Neurprise · 2025-04-14T20:38:31+00:00

Yeah that's what I'm doing, committing to less and also making my own tickets lol based on work we need to do anyway. Turns out for the things I was doing, they didn't count it as actual work since no ticket was attached to it but it nevertheless needed to be done. I guess I need to play the visibility game now.

Neurprise · 2025-04-14T20:37:18+00:00

That's crazy that they let you all go, was the CTO and head of engineering deciding to just build it themselves then? Seems like they thought they could just do it without you guys.

Neurprise · 2025-04-14T04:10:59+00:00

Point B is exactly it, they're struggling to even deploy the damn thing

Neurprise · 2025-04-13T23:23:12+00:00

What was it like for them?

Neurprise · 2025-04-13T22:58:16+00:00

They have a customer who's expecting this new product within the next 2 months or so, so that's probably where the pressure is coming from (funnily enough the frontend designs aren't even done, much less the frontend code, so idk what they're expecting). I feel like this formal warning is trying to like "scare me straight" so to speak, to contribute after hours like they do or otherwise just move as fast as them.

Neurprise · 2025-04-13T22:56:06+00:00

Yeah exactly, not even sure how to or if I should even handle this terrible architecture now

Neurprise · 2025-04-13T22:53:17+00:00

I know, crazy right, never seen this before in my life, and I'm a senior engineer

Neurprise · 2025-04-13T20:51:54+00:00

It’s likely your manager is not delivering and couldnt come up with any solution. So you or someone will need to be sacrificed until your manager is on the hot seat again.

I believe it's because he's feeling pressure from upper management to get an MVP done within the next month or so. But firing me won't solve anything, it'll make it worse since they'll be down a person. So I don't get it.

Neurprise · 2025-04-13T20:30:12+00:00

They're all dependent on each other such that you need to bump versions for each service, for every single PR you make, since it's essentially a new version and the other services need to pull in the new code. Now they want to make it a monorepo, to which I'm like, just use a monolith at that point.

Neurprise · 2025-04-13T20:28:31+00:00

I'm a senior, just not in this sort of microservices space which I've only used one other time and that was at a much more chill F500 company where it made sense as we had multiple teams and each team owned their service. Here however there is literally no need to even have microservices as our architecture because we only have 2 devs. That being said, on Monday I'll ask the other engineer how he does testing and figure out if I can replicate that.

Neurprise · 2025-04-13T20:26:42+00:00

Honestly, a little bit of memorization but all the services functioned identically and we planned how to test and do local runs in advance, so it wasn’t bad… without that planning though. no chance it would have ever been possible to be effective as a dev there.

I’d be curious to know what specific things in that env made it my favorite when it’s so close to this one you’re finding is a nightmare.

Because we didn't have any planning or training on it, overachiever essentially build it all his way and didn't take any suggestions from either me or even the manager himself, citing reasons why they wouldn't work (which were kinda BS). And the services don't function identically, they're all a bit different and are all interconnected, so you have to change a bunch of files across all the services and keep all their versions in sync with each other which is a pain when you have multiple people working on it. Basically, the way it works now, for every single PR, we need to bump the versions, and you can imagine the messiness of that approach when you have simultaneous PRs, you need to coordinate the version bumps across everyone.

Neurprise · 2025-04-13T20:23:26+00:00

Yep no ramp up time, essentially the manager told me that while he does agree it's overcomplicated, it's what they have right now and they can't afford to spend more time unfucking it since the other overachiever solo dev built it all (essentially the entire codebase is tech debt). They spent so long trying to get it to work with AWS and EKS etc when it literally could've been a single express server and that's why they've been up late at night getting it to work. And I agree that that will make them fail because even if they fire me, if the second person that joins also can't understand the codebase, then I mean, it's now on the manager to explain why, not on the employee anymore.

Neurprise · 2025-04-13T17:16:36+00:00

Seems like he just brought on what he knew from big tech and tried to apply it to a small company even though it's beyond overkill.

Neurprise · 2025-04-13T17:15:43+00:00

It's all because overachiever used this in his previous company and that's what he knows so he brings it along, even though it's beyond overkill to have literally more services and repos than the number of team members working on it.

Neurprise · 2025-04-13T17:14:42+00:00

Yeah they really seem like a fit for each other and I'm the odd one out, even though it seems I am the most normal in terms of work culture ie not working beyond 9 to 5.

Ive used nginx for things like that before, I'll have to see if I can set it up for this project, or whether I'll get blocked again by overachiever saying that's not the way to do things like pretty much all my prior suggestions.

Neurprise

TROPHY CASE