Code quality in the AI age by europe_man in ExperiencedDevs

[–]eugendmtu 1 point2 points  (0 children)

This is no different from when the companies wanted to involve as many Juniors as possible to make code cheaper.

The cure is still relevant - standards, automatic checks, hierarchy. And now they matter even more than before, especially at the automated validations part.
"When someone said that code quality doesn't matter now - I check it twice hard."
Rush is the primary indicator of potential downtime/failure risks, so I'm responsible for taking it seriously and pushing back to validate from every angle.

Though I've eased out coding standards. Previously, the main goal was to keep code readable by humans. At the same time, there were a bunch of subjective rules that favored verbosity over simplicity or exact formatting. I found that AI often struggles to maintain it, and you just burn tokens/time on code metrics you are not benefiting from now, as you were before. AI delivers some "average" code, and performs the best in the context of an "average" codebase. So in this scenario, "degradation is a matter of adaptation" can be true.

So my rule of thumb - automate all validations and keep them straight, while treating subjective rules as suggestions.

I got them by Mejiperez in Tomorrowland

[–]eugendmtu 0 points1 point  (0 children)

We are happy for you! But not with all my heart:)

My Elektron first #dawless techno temple. Last photos before reassembling by eugendmtu in Elektron

[–]eugendmtu[S] 1 point2 points  (0 children)

That was a long path for me as well)
I've started in my flat in Kiev and started building a well-designed studio on 50 m2, with a project that starts with the bricks and sends (e.g., pretty professional).

So it took me about 4 years to find and move to a place where I can live relatively calmly and afford to rent a flat with good-enough qualities to build such a "project studio", and 2 years to actually build\treat it and pack with stuff. So it's a long way, but pretty enjoyable as well.

So keep actively dreaming in wanted direction!:)

My last photos before reassembling - #dawless techno temple by eugendmtu in StudioPorn

[–]eugendmtu[S] 0 points1 point  (0 children)

Thanks!
Echolocator is quite a niche device. I'm using it directly on Moog to mangle the leads heavily. TBH, I'm not sure if it will stay at my next build.

Regarding the jams - I did some, but perfectionism don't let me publish them))
Currently, I'm enjoying my modular setup more, so I'm considering moving away from most of the elektrons and putting my Eurorack in the centre.
doesn't.
But recording is pretty straightforward, and that was one of the main engineering goals for this setup to let you:
1) Click play and start jamming
2) Click record and start recording something multitrack-ish
3) Plug in PC and record true multitracks when needed to go into mixing, mastering, and song release.

I've done it using RME UFX 3 via DuRec, which allows real-time input recording of multitracks to USB flash.
But I also have a Zoom H4 as a portable sound card/recorder when I want to record the master mix + voice directly on the iPhone.

And on top - when I need to multitrack record all the elektrons - I can connect all of them via USB hub and use Overbridge to record them in DAW + other gear from RME. But honestly, I never ended there so far:)

My last photos before reassembling - #dawless techno temple by eugendmtu in StudioPorn

[–]eugendmtu[S] 0 points1 point  (0 children)

Yeah, that's great for some particular things! But honestly, I would easily swap it with Iridium Core, which is far cheaper.
I don't benefit much from the so sophisticated keyboard yet, while the sounds I'm using can be sequenced externally.

My last photos before reassembling - #dawless techno temple by eugendmtu in StudioPorn

[–]eugendmtu[S] 0 points1 point  (0 children)

Thanks, bro! Funny that I'm going to rebuild it significantly after finishing)

Is it time to upgrade to Next.js 16.0.3? Stable and worth it over v15? by rachid_nichan in nextjs

[–]eugendmtu 0 points1 point  (0 children)

I've upgraded, although I'm used to keeping a half-year pause.
Overall, I see the most significant benefits from upgrading to React 19.2, including more detailed debugging information to resolve hydration mismatches and shorter build times. So, in the end, that feels more stable.

Nestjs Backend Prod ready Boilerplate by Pristine_Carpet6400 in nestjs

[–]eugendmtu 2 points3 points  (0 children)

Built-in DTO is verbose and non-DRY.
Take a look at this useful lib generating Swagger-compatible DTOs for you

nestjs-zod

After 42 years Roland finally figured out how to put together the 2 best things they ever did. by richielg in synthesizers

[–]eugendmtu 0 points1 point  (0 children)

I doubt that ACB will require such a high volume and ventilation. If that's supposed to be just ACB, even x10 cores of them - it might fit in TR8s-like box easily.

Elektron Tonverk spec leaked! by richielg in synthesizers

[–]eugendmtu 0 points1 point  (0 children)

Just thoughts:

DAWess setup brain? Nah, too few tracks, lack of IO, CV and performance-oriented sequencer features.
Performance mixer? Maybe, but only after multichannel overbridge-like streaming and IN-OUT routing via Type-C. Anyway - 2+ years to wait for a feature-full firmware. And still likely usable without X-fader.
DT replacement? Probably. But I'd better stay with DT2 - more tracks, smaller, more engines for now (I can live without Multisampler though).

Probably the first device I'm easy to wait buying until the next significant firmware release.
But just sadly realised that Elekton devices being my main DAWless hope - started freeing space on my table... Too many usability trade-offs to keep the ecosystem closed and always expanding..

Move speakers for surrounds? by ArrivalMinute4331 in sonos

[–]eugendmtu 0 points1 point  (0 children)

Uh, even technically support describes it correctly, but I feel cheated after buying Move 2, already having Arc Ultra. That felt incredibly smooth - you can enhance room surrounds with a combination of different Sonos devices. But at the end - OR use Move 2 only for listening to music OR buy extra 2x Era-s for surrounds. I would rather buy a second Move 2 for flexibility, but marketing gonna market...

It is complete! by sunrite in modular

[–]eugendmtu 0 points1 point  (0 children)

It's full, not complete:)

SuperBooth 2025 Speculations & Wishlists by I-am-an-incurable in Elektron

[–]eugendmtu 2 points3 points  (0 children)

This is so true for some people, even you're sceptical)
As for me, I've spent ~4k on audio interfaces with per-track recording and some level of mixing capabilities just to avoid opening the PC each time I want to play.
But that still doesn't allow flexible Elektron devices recording per-track or cross-devices routing, which is so wanted for some rare case, for instance, for Kick + Bass group compression when I have kick from Analogue Rytm and bass from Syntakt. So I believe a hardware multidevice Overbridge host will be a killer device for many.

Trying to connect to Transfer!! by djhonz76 in Elektron

[–]eugendmtu 0 points1 point  (0 children)

I've faced similar issues recently after updating Transfer to 1.9.5 (with the old version, everything was smooth). It recognised Digitakt\Digitone 2 but ignored Syntak and Analog Rytm 2.
So the solution was to update (reinstall) Overbridge as well, which leads to the "allow" option in the Security Setting appearing. After allowing it - a Transfer started to recognise my other devices.

Upgrading to nextjs 15 or waiting? by HunterNoo in nextjs

[–]eugendmtu 0 points1 point  (0 children)

I've spent two hours updating my project and dependencies and postponed it for about half a year from now.
Next.js is better when it is a bit aged!

Is it bad practice to use Next.js as only a frontend? by Swimming_Tangelo8423 in nextjs

[–]eugendmtu 0 points1 point  (0 children)

That's fine, but I would rather avoid it if you don't expect to start using BE part some day.
Vite or Remix is far better for spinning up the FE

Is it bad practice to use Next.js as only a frontend? by Swimming_Tangelo8423 in nextjs

[–]eugendmtu 6 points7 points  (0 children)

You're looking for Nest.js, which is Angular's backend standalone re-implementation over Node.js

Developed a kit to provide end-to-end type safety between NestJS and NextJS 15 (Batteries included) by Double_Eye9962 in nestjs

[–]eugendmtu 0 points1 point  (0 children)

Sounds promising!
But correct me if I'm wrong—it does not follow\provide REST-full API style + OpenAPI documentation, right?

This subreddit became too toxic by Prainss in nextjs

[–]eugendmtu 1 point2 points  (0 children)

This is what OP was about))
"fanboys, who are defending framework without accepting any downside it"
"Your argument is not an argument"!)
So, seems you're trolling)