쉐도잉 연습: Why 95% of Android Developers Get Use Cases Wrong - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
Hey guys and welcome back to a new video.
2
95% of Android developers use use cases wrong.
3
It's a catchy title, but I really mean that number.
4
I will tell you why.
5
Because use cases on Android and in software development in general are so often misunderstood.
6
I also myself misunderstood them when initially getting into these.
7
I'm pretty sure you can still find some super old videos on my channel where I'm also making the mistake
8
that I talk about in this video.
9
If your use case looks like this to get some user information, then you are doing it wrong.
10
Why is that?
11
In order to understand what use cases should contain and what kinds of use cases you should create, if you decide to stick to use cases,
12
we need to understand what a use case is originally meant to be in the context of software engineering.
13
And if we actually just Google for that, use cases software development, and we just click on a random picture here, then we have, for example, a library information system.
14
And then we have some use cases.
15
This is what we call a use case diagram.
16
Maybe you remember that from university or so.
17
to browse books, checkout books, return books, update the catalog, clicking here, view items, make purchase, checkout, client register.
18
If we carefully think about these use cases here, how they are named, view items, browse books, checkout books, what do all these have in common?
19
They all have in common that the user is actively aware about these things happening
20
because it is a real use case of your app.
21
And if you have a use case, then you can use it as a user.
22
Now, when we talk about email validation, is that a use case?
23
Is this something where a user would go to your app and now say, ah, now I'm going to validate my email, or now I'm going to clear my session.
24
Or hey, now I will retrieve a user by its ID.
25
No, they actually have no idea that these things happen.
26
These are rather just side effects of a real use case.
27
The user definitely knows that they are currently registering an account.
28
And email validation is just a side effect, something that happens as part of registering an account, but it's not something that the user actively has in their mind when they go through registration.
29
So if we take a look at some real use cases, the way it's really intended here on the correct, then we, for example, have this register use case.
30
And you can see suddenly it starts to contain real logic.
31
It's not just a single line of code that calls a repository or some kind of validation class, but it's a real use case that combines multiple pieces of business logic into a use case,
32
into something the user can do with your app that they are aware about.
33
So this would be a good example for a use case because the user knows that they are registering an account.
34
Of course, what's part of the use case is actually validating the email.
35
It's validating the password.
36
It is actually making the call to our remote API, for example.
37
It is then handling the errors and actually forwarding these to whatever class calls this use case.
38
That is a good example of a use case.
39
Well, let's take a look at this logout use case a user certainly knows that they are logging out.
40
But what internally happens as part of logging out, like actually making the network call, clearing the session, clearing their shopping cart, that's something they don't know and they don't have to know.
41
So the use case actually just bundles these function calls and makes sure that they are executed in the right order.
42
So we have a reusable kind of package for logging out and we just need to invoke the logout use case.
43
So other parts of our app also don't need to know what internally happens when we log out.
44
And all these other classes that act as utility for our use cases, like validating an email, this is of course still business logic.
45
This still lives in your domain layer, but it's not a use case.
46
So you really just make this a plain class, call it whatever it's responsible for, email validator, password validator, and then suddenly use cases make a lot more sense.
47
As you know, I'm usually not for using use cases a lot
48
because you will still often have these pretty much empty use cases, even when doing it the correct way.
49
So for example, if you say you want to fetch your nodes, so you actually want to see the nodes as a list, and then there's usually just a call to a REST API.
50
So you just forward this to your repository.
51
There's no error handling or so.
52
Maybe the repository already handles that, but no real business logic error handling in the use case itself.
53
But there are certainly use cases that make a lot of sense.
54
Like here, bundling these different calls here into a logout use case makes a lot of sense
55
because you will never again have to memorize what logging out really does in your app.
56
Instead, you just call this use case.
57
You never have to memorize what registration actually means and does in your app, unless you're, of course, responsible for working on that part.
58
But you can really just invoke the use case
59
and you know the use case involves the business logic to take care of that.
60
And if you stick to use cases in your app and you actually stick to them like this the right way, then I don't have a big problem with that.
61
Still, I personally lean more towards not using them at all
62
and just also bundling such business logic either in the view model or the repository, at least for small to medium-sized projects.
63
But for larger projects, this can make a lot of sense and I would also really consider having use cases there.
64
Now, if you feel like, okay, there is still a lot to learn about Android architecture, about Kotlin multi-platform architecture, then I can help you with exactly that
65
because we have our senior app developer mentoring where you get to build a real production project over multiple months
66
and have all your code reviewed by your personal mentors, including me.
67
This way we can spot issues in your app's architecture.
68
You actually have no idea about that these even exist.
69
If you're making mistakes you don't know of, then you obviously can learn from these mistakes.
70
So this is really a fast lane program here for you to grow to a senior developer level.
71
Link is below.
72
You can apply to this program.
73
We can have a chat if this could be a fit.
74
You can't just buy it on that website like a course, but we really first of all have to talk if we can help, how we can help, how it makes sense for you in order to also craft an individual learning plan for you.
75
So take a look at that.
76
Thanks for watching and I will see you back in the next video.
77
Have an amazing rest of your week.
78
Bye bye.
📺 같은 채널
✨ 추천 영상
C11
126 문장
How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes
University StudentsBusiness English+1
C12
119 문장
How to Write Test Cases for Manual Testing?
University StudentsBusiness English+1
C115
23 문장
The future unfolds! How to optimize Android apps for adaptive layouts
University StudentsBusiness English+1
C11
207 문장
How I Made $30,000 Hacking Broken Access Control
University StudentsBusiness English+1
C11
283 문장
My UX Design Case Study Presentation that Got Me Hired | Case Study Walkthrough
University StudentsBusiness English+2
C12
172 문장
DRY Often Makes Your Code Worse
University StudentsBusiness English+1
C14
164 문장
System Design Mock Interview: Design Facebook Messenger
University StudentsBusiness English+1
B21
75 문장
Video
University StudentsBusiness English+2
C14
239 문장
My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It
University StudentsBusiness English+1
B21
87 문장
Introduction To Marketing | Marketing 101
University StudentsBusiness English+1
B21
64 문장
JTBD Framework in UX w/ Examples | UXtweak
University StudentsBusiness English+1
C14
206 문장
New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets
British Accent, en-GBUniversity Students+2
실생활 시나리오: 개발자들의 실수와 올바른 사용 사례
이 비디오는 안드로이드 개발자들이 95%나 사용 사례를 잘못 이해하고 있다는 주제로, 소프트웨어 공학에서의 사용 사례의 본래 목적을 설명합니다. 사용자가 직접 인식하고 행하는 '회원가입', '로그아웃'과 같은 행위가 진정한 사용 사례이며, 이메일 검증이나 세션 정리와 같은 것은 그 부수 효과에 불과하다는 점을 강조합니다. 이를 통해 개발자들이 비즈니스 로직을 올바르게 구조화하는 방법을 알려줍니다.
유용한 구문과 연어
- use case: 사용 사례 (소프트웨어에서 사용자의 목적을 달성하기 위한 일련의 행위)
- business logic: 비즈니스 로직 (애플리케이션의 핵심 기능을 구현하는 규칙과 프로세스)
- side effect: 부수 효과 (주요 기능 외에 발생하는 추가 작용)
- remote API: 원격 API (인터넷을 통해 다른 서버와 통신하는 인터페이스)
- domain layer: 도메인 계층 (애플리케이션의 비즈니스 로직이 위치하는 계층)
당신의 쉐도잉 챌린지
이 비디오의 대화를 듣고, "use case", "business logic"과 같은 키워드를 포함한 문장을 반복해서 따라해보세요. 특히 발음이 어려운 단어는 천천히 들으면서 입 모양을 확인하고, 영어 발음 교정에 집중하세요. 쉐도잉 사이트나 shadowspeak와 같은 도구를 사용하면 더 효과적입니다. 3분 동안 매일 연습하면 IELTS 스피킹 실력도 향상될 뿐만 아니라, 자연스러운 영어 표현을 익힐 수 있습니다. 오늘은 "The user definitely knows that they are currently registering an account."라는 문장을 5번 이상 따라해보세요!
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.