Victor Rentea

Пікірлер

@SmallcampusTin 13 күн бұрын

This is amazing. Thank you Victor and Oleksandr.

@kalamatej 15 күн бұрын

Amazing how closely your prophecy about the developer transition from favoring mock testing to integration testing matches my experience 😊

@lts8683 15 күн бұрын

I love you ❤

@iliyan-kulishev 2 ай бұрын

You mentioned that CQRS has ruined the life of many teams. Why is that ?

@audiobooks97 2 ай бұрын

really great points to check when reviewing a PR - thanks for the info!

@VerhoevenSimon 2 ай бұрын

Thank you for the interesting session.

@lts8683 2 ай бұрын

Thanks for your efforts ❤

@audiobooks97 2 ай бұрын

Thanks for sharing the video! Understand the design pitfalls give a full stack developer like me valid considerations to think about!

@sharifyy 2 ай бұрын

When using uuid, considering an extra id(uuid) in database is better or just use the uuid as primary key?

@hareepjoshi 3 ай бұрын

Hey victor, the rest calls could have also been wrapped into a callable that is run on a bounded elastic thread. isn't that so? REST calls are not reactive and are in fact every bit as blocking as hibernate.

@scoobydooby4672 6 ай бұрын

can someone tell me what is Kata?

@vturcan 6 ай бұрын

Thanks for ctrl+shift+i !

@self-aware986 6 ай бұрын

Interesting and entertaining talk!

@i-am-the-slime 6 ай бұрын

What a backwards way to look at this. Java is the weird one that requires an object everywhere instead of having functions like every other PL in the world. God Java is so bad.

@i-am-the-slime 6 ай бұрын

referential is the word

@bbravoo 6 ай бұрын

Happy to see that Victor is stating to love Kotlin ♥

@moonbiscuit8742 6 ай бұрын

I'm working on a project which has banned throwing exceptions and abuses the Optional/Result pattern in a bad way. We're not even using it in a very functional way - there is no .Map() on it. Every method call is followed by the same mindless if() checking of the result and bubbling up the error to the top level - it's not that callers can even handle the optionality. Introduces a huge amount of useless code surface serving as distraction. Honestly don't understand why nobody questions this. I tried to bring it up, I get my favorite reply - "let's keep it consistent".

@i-am-the-slime 6 ай бұрын

Why don't you use a monad transformer?

@aoeu256 6 ай бұрын

Pretty awesome, I wish we could upgrade code from one language to another when we figure out better ways of developing stuff. Julia also looks pretty awesome, its a LISP but with infix syntax. You can use Clojure in a Java project by telling people that S-expressions are XML 3.0, and sometimes you can try using a cross-compiler to change your clojure to Java if they get suspicious. Its awesome you talk about the Either problem (checked Exceptions) in Haskell, its a problem in Haskell with *ALL* containers including Maybe and all other Monads, however, Haskell is more consistant so I maybe there is a solution to it (Algebraic effects somewhat fix it), while Java lacks referential transparency everywhere so maybe that may change things.

@Natalicha1234 7 ай бұрын

Such a cool discussion! Thanks!

@kennystephen8481 7 ай бұрын

Thank you, I found this video very interesting and your presentation is just unique.

@tonino_nelveneto 7 ай бұрын

Thanks victor for share such content !! 👍

@rodneyreynolds7705 8 ай бұрын

😥 'promosm'

@RamySharaiyri 8 ай бұрын

Extract PERFORMANCE AND CONSISTENCY outside of your domain -> then Clean code has place in your project :)

@hartmut-a9dt 8 ай бұрын

7:10 SQL ... why should this ever skipped... it is so nicely declarative. way more declarative as many other programming paradigms.... and stable for decades. Nicely demonstrated. many thanks for sharing the debate! Inspiring! i am opting for small teams, DevOps, Microservices. No big pillars, split between UI and Backend etc. And Requirements, Business oriented development over and microservice generations.

@jeanfelipesorio4992 9 ай бұрын

This is the kind of guy I would trust the architecture of my project

@venura79 9 ай бұрын

Check eventmodiling its another variation of event sourcing

@kasparsr 9 ай бұрын

Navigating code that is based on events seems to be harder than method calls. And like in reactive programming stack traces are not very useful. Is there any tips to simplify that? I was in a swing project with many events. And we rewrote it to simple method calls.

@tzagasdog 9 ай бұрын

is there a repo showcasing the code demonstrated?

@A3A3adamsan 9 ай бұрын

It's weird. I have this video in my browser history in jan. 6th, where the subject was about event storming a covid vaccine application. Is it how youtube live works? If you stream a new, will it override the previous one with the same name?

@Tom-tn9cf 10 ай бұрын

Great talk, are there any strong examples of this online in a git repo that you can share ?

@RaphaelSousa-or1dl 5 ай бұрын

I'm also interested in that, have you find any good examples?

@tsiyon12 10 ай бұрын

“There’s a lot of me”, yeah but you’re probably average height for a Dutchman 😂

@ionut-cosmingradinaru5514 10 ай бұрын

Awesome👏

@PushpakMittal-rt1il 10 ай бұрын

This is the best someone has ever explained Java concurrency.

@ijazfx 10 ай бұрын

First of all, amazing talk. Really enjoyed and learnt a lot. yes we do have systems which use 500K TPS, e. g. sending 500K subscribers SMS campaign and it has to be instant. What is your suggestion? We are planning to use VT.

@florinake85 10 ай бұрын

as always great content, keep up the good work Victor!

@pavelbiryukov1095 10 ай бұрын

Viktor, thanks, very interesting and funny as usual :) what's the drawing on screen application? :)

@A3A3adamsan 11 ай бұрын

To me the context menu doesn't contain "Try to generify" or any of the other options. I only get the "introduce local variable". Is this the Ultimate Edition, or did they make IntelliJ worst? Or am I missing something?

@mihaiapostol7864 6 ай бұрын

i think you get just the options that are possible with the current code that you highlight. also, this video was filmed 3 years ago so IntelliJ has changed a lot since then :)

@GRHmedia 11 ай бұрын

How do you know those test cover everything? They don't those tests you just wrote are code also what is testing them? TDD is a practice in insanity. I've seen people screw up writing the unit test. So what next are you going to write more test to test that? TDD is a moronic concept!

@GRHmedia 11 ай бұрын

Why right test first? 1. So I can milk this job and get more pay. 2. I'm an amateur and unreliable in my coding skill. 3. I like bloated code. 4. I like poor performance and lots of if and else statements.

@TheTubeYou251 11 ай бұрын

You can have a method like activate with immutable objects as well. You just have to create a new copy with the fields status and activatedBy changed.