Before opinion: 10x dev might exist (even 1 of the points might be enough): - in specific domains (and tooling) with expertise - if he/she is really into programming (work AND hobby) - if has access to knowledge networks (someone working at Meta / Google / just with really good coworkers)
Can I suggest a video? Would make one related to testing with playwright/cypress on the topic of avoiding flakiness in tests? I've been speaking with friends and most of them are putting retries to cover flaky tests. I have never seen a content that helps us write less flaky tests in both tools. Thanks!!!!
Good content! It's great to see you're following your followers recommendations, which is rare on TH-cam today. Without a doubt, this will help you stand out in the developer community. BEFORE WATCHING THE VIDEO: Yes, the 10x developer is real, developers that don’t just code manually, they master metaprogramming to generate code automatically when needed. They write scripts that can dynamically modify or create files by analyzing the existing structure of codebase classes, files, database tables, columns, and more. How? Using techniques like reflection, static code analysis, abstract syntax tree manipulation, introspection, domain-specific languages (DSLs), code generation by custom compilers. Nothing accelerates code output better than machines designed for this specific task. The programmer simply orchestrates the process, letting the machine handle the heavy lifting. The industry generally doesn’t favor developers who work this way, as it’s quite different from the typical approach used by most professionals today... AFTER WATCHING THE VIDEO: I feel like I was imagining the "100x dev" in terms of hard skills, but the video focuses more on aspects related to soft skills, which are crucial when working within teams.
Another great video man, keep it up!! What people fail to realize is that doing the minimum don’t guarantee the health of the product, aka their own work! That’s where the “owner mindset” they request on the interview comes up 😅
Whoever doesn't think 10x exists, already died from inside. Not always we will be 10x, life happens all the time, but giving up on that is the worst. Just be careful not to be 10x in a shitty company; otherwise, you will receive feedback like "you care too much." That single boss put me into a big burnout that took me a long time to recover. Beware of people trying to put you out of 10x!
Thanks for describing me! The only thing I'm lacking a bit is in the test department. But that's going to change as I'm frutrated with the lack of testing we have and the amount of DUMB issues we get. :D
@@Metruzanca I have to admit that only recently I started “enjoying” writing tests. Once you start seeing the positive side, which is giving you more confidence, then you start wanting to write tests instead of just feeling obligated to do it
BEFORE: 10x developers are overhyped, but there competency is a spectrum. A person is good at some things, and really bad at others. For example I'm decent at figuring out what stakeholders want, and then couple together libraries and tools to build the features and functions to suit their needs. But ask me to do some low-level graphics programming and I'll just go and cry in the corner instead.
HAH the story time is funny, because I always include a reference to the ticket I'm fixing in my PR, but its usually because I want to give my reviewer as much information as possible to understand my Pull Request. Its a constant fear of mine that my PR looks crazy! So I always add a good PR body describing my changes, add references to requested work etc, links to docs of packages beign used etc
I was caring deeply about my craft, now i just ship it if it works
I am a bit of both. Because I want to release good product fast I made my own starter kits so I can just focus on the specifics for each project
AFTER: You're absolutely right about the attitude - that is what makes or breaks this whole thing, and everything gets derived from that.
After opinion: 10x dev follows your channel :)
Before opinion: 10x dev might exist (even 1 of the points might be enough):
- in specific domains (and tooling) with expertise
- if he/she is really into programming (work AND hobby)
- if has access to knowledge networks (someone working at Meta / Google / just with really good coworkers)
Can I suggest a video? Would make one related to testing with playwright/cypress on the topic of avoiding flakiness in tests? I've been speaking with friends and most of them are putting retries to cover flaky tests. I have never seen a content that helps us write less flaky tests in both tools. Thanks!!!!
I'd second that.
Good content! It's great to see you're following your followers recommendations, which is rare on TH-cam today. Without a doubt, this will help you stand out in the developer community.
BEFORE WATCHING THE VIDEO: Yes, the 10x developer is real, developers that don’t just code manually, they master metaprogramming to generate code automatically when needed. They write scripts that can dynamically modify or create files by analyzing the existing structure of codebase classes, files, database tables, columns, and more. How? Using techniques like reflection, static code analysis, abstract syntax tree manipulation, introspection, domain-specific languages (DSLs), code generation by custom compilers. Nothing accelerates code output better than machines designed for this specific task. The programmer simply orchestrates the process, letting the machine handle the heavy lifting. The industry generally doesn’t favor developers who work this way, as it’s quite different from the typical approach used by most professionals today...
AFTER WATCHING THE VIDEO: I feel like I was imagining the "100x dev" in terms of hard skills, but the video focuses more on aspects related to soft skills, which are crucial when working within teams.
Another great video man, keep it up!!
What people fail to realize is that doing the minimum don’t guarantee the health of the product, aka their own work!
That’s where the “owner mindset” they request on the interview comes up 😅
Whoever doesn't think 10x exists, already died from inside. Not always we will be 10x, life happens all the time, but giving up on that is the worst.
Just be careful not to be 10x in a shitty company; otherwise, you will receive feedback like "you care too much."
That single boss put me into a big burnout that took me a long time to recover.
Beware of people trying to put you out of 10x!
This 100%
Thanks for describing me!
The only thing I'm lacking a bit is in the test department. But that's going to change as I'm frutrated with the lack of testing we have and the amount of DUMB issues we get.
:D
@@Metruzanca I have to admit that only recently I started “enjoying” writing tests. Once you start seeing the positive side, which is giving you more confidence, then you start wanting to write tests instead of just feeling obligated to do it
@@DanielBergholz When you learn about property-based testing, there is more fun! Of course, Elixir has an awesome lib called StreamData
BEFORE: 10x developers are overhyped, but there competency is a spectrum. A person is good at some things, and really bad at others. For example I'm decent at figuring out what stakeholders want, and then couple together libraries and tools to build the features and functions to suit their needs. But ask me to do some low-level graphics programming and I'll just go and cry in the corner instead.
I think I'm a 10x developer, just lacking the knowledge 😂
THIS IS THE WAY
HAH the story time is funny, because I always include a reference to the ticket I'm fixing in my PR, but its usually because I want to give my reviewer as much information as possible to understand my Pull Request. Its a constant fear of mine that my PR looks crazy! So I always add a good PR body describing my changes, add references to requested work etc, links to docs of packages beign used etc
@@Metruzanca I have many horror stories to tell in the next videos 😂
But yeah, the maximum amount of context you can give in the PR the better!
It's not only a context for others. It's a context for your future self.
Visão!
E o inglês tá o fino do fino
@@2viniciusms obrigado!
Ok but seriously whats testing
Excellent question, once you find the answer, LMK! 😅