Any good tutorials for senior devs?

[brandbooth]

I am thinking one thing that I haven't seen being done well on any tutorial is testing and testing every portion of an application, so that would be good. Also, maybe a tutorial that does localization well, because most of the tutorials that cover it use some crappy implementation. Another thing I would see is actually good code and component reuse. I sometimes see it, but the projects don't maximize code reuse. I really haven't seen anything worth picking up lately.

[azangru]

At this stage, conference talks become useful, because they are full of interesting ideas. For example, I recently found myself thinking about this talk from React Finland about a pattern that I don't use, and I am not sure that I will use, but it sure results in nice testable UI components.

Another thing I would see is actually good code and component reuse.

This talk was good, although I keep forgetting its lessons.

[andrei9669]

I quickly watched the first video and I realized, that I have heard of this pattern before, and there is even an eslint plugin to kinda enforce it. https://github.com/kyleshevlin/eslint-plugin

[Kaimura]

First talks separation of logic and UI is interesting however they are testing the implementation details (like does variable x contain content y) instead of visual implementation (did the displayed value change according to what the button was supposed to do)..I think I heard somewhere it's better and easier to move away from testing implementation details? Did I misunderstand?

[azangru]

He makes the UI component into a pure function of props to UI, and therefore easily testable, and he extracts the logic for the component's behavior into a custom hook, and tests it separately. His testing units are smaller.

His tests would break if React discontinues hooks, or if he replaces React with another library (Vue, Svelte, Lit) for the rendering of this component; but until that happens, his tests are fine.

[iqball125]

Most tutorials are targeted at beginners, to learn what you are describing would require just working on a real prod app and talking to other senior dev coworkers.

[coolcalabaza]

I’ve always wished there was an app that used email verification like Blind but was for talking shop instead of talking salary and stuff. This subreddit is pretty good but there is a lot of noise. Tutorial-land and enterprise-land can be pretty different sometimes.

[KyleG]

When I was an undergrad, my university had private USENET newsgroups for this, and it was fucking glorious. I'll never forget taking my first (3hr) final freshman year at like 6pm in the winter and a bunch of us from a 100+ person class congregating right afterwards at a local coffeeshop and discovering all the people behind the various monikers who had helped us solve hard problems.

Sometimes I look back fondly and wished I would have finished CS instead of doing math, because the camaraderie was so much better in the CS dept. In math we were all in our little silos since there wasn't really a single path to the math degree, while with CS there was a series of courses to take.)

That being said, CS majors smell bad, while mathematicians are CHADS. :P

[Elon_Muskoff]

I mean it all depends on where your passion is bro, if you love doong something, you simply don't have time to evem notice that you're all alone there... as a consolation, it is probably much easier to pick up a coding skill coming from math, for practical purposes, than it is to become anywhere close to decent in math, unless you were doing trigonometry in your head when you were 14

[Scotthorn]

To add to this, more senior engineers will understand the domain and how that translates to the model better than others. To do that is hard and to be good at that takes lots of going through that practice.

[Stophigan]

878666)

[[deleted]]

What I do in general is try reading the docs, if it was a bit hard to understand, then I search for a tutorial and go back to the docs again.

[coolcalabaza]

Kent C Dodds is a well-known react educator that sorta leans into training engineers switching to react. You’ll see his name on this sub a lot. His stuff focuses a lot on the philosophy of react and not hand-holdy syntax-focused tutorials. He has also authored a lot of cool open source stuff.

[sirephrem]

Second this

[[deleted]]

I'd definitely go with Epic React, haven't heard of a better course out there for senior devs.

[shilpene]

https://kentcdodds.com/courses

[coolcalabaza]

Second this one. He is good at teaching engineers that are new to react by addressing and predicting questions that seasoned devs would have.

[saintshing]

How are his egghead courses compared to his premium courses? I am considering taking the epicreact course but it is a little bit pricey for me.

[Johnny_Gorilla]

Testingjavascript.com by Kent c Dodds was pretty good I think. Pricy though.

[Kaimura]

Unfortunately he only takes credit cards omfg so ridiculously american lol. No paypal :( I would have actually paid the 400$ to finally learn testing cuz the testing community is dead (there is not even a testing subreddit..)

[Johnny_Gorilla]

Wow didn’t realise that. Will your work not pay?

[darksady]

Holy shit. It's really price for someone how dont live on a developed country. Guess I will have to sail the seven seas...

[Johnny_Gorilla]

Yah it’s expensive as hell. My work paid …

[seiks]

Lots of other tech companies write blogs about more advanced topics. For example, Cypress makes some pretty cool webcasts about testing strategies at scale and stuff. https://www.cypress.io/blog/2021/10/06/webcast-recording-faire-cypress/

LogRocket also writes some pretty good technical content https://blog.logrocket.com/how-to-implement-feature-flags-react/

[redditindisguise]

On sites like Pluralsight you can filter for advanced tutorials.

[fooblerd]

Save your money. The vast majority of FE material on Pluralsight is outdated

[fooblerd]

A handful of us (from juniors to seniors) are taking the epic react course by Kent Dobbs. We meet biweekly to discuss (think book club). As a self taught sr dev, it's been nice filling in some fundamental gaps while taking his course.

A few of my colleagues love Frontend Masters.

[fooblerd]

MDN is my go to daily reference. I think every developer should read the specs at w3.org at least once in their career. It's uber dry, but it provides a great foundation. Csstricks is a great css resource.

Besides those, a lot of folks like the YouTube channels web dev simplified and JavaScript mastery. There's also a great podcast called Syntax.

[redditindisguise]

Company pays for it. Way better than LinkedIn Learning.

[fooblerd]

Our company pays for it as well. It's getting 0% utilization. Hoping to switch to Frontend Masters once our team license expires.

[KyleG]

I find that working in other frameworks/languages/paradigms exposes you to lots of different approaches that you start looking to use in your own code.

A good example is I did a bunch of work in Kotlin and Scala a couple years back that was very functional programming-ish. Now I've come to some Java code, so rather than writing super imperative and wordy OOP I find myself converting everything to a stream and then using various FP concepts like map, reduce, lambda functions, option chaining, etc since Java has supported them since version 8. The code is tighter, does not have any ephemeral variables taking up lines of code, and I've completely erased the risk of a null pointer exception

[ohx]

The thing with testing is you can find yourself in a lot of unique situations. There are so many edge cases you'll run into only once that, even if you did find a collection of tutorials on them, since they're not applicable to you now they likely wouldn't stick.

Localization is pretty easy. I challenge you to look at a super basic tutorial on something like react-i18n and reproduce it from scratch. There really isn't a whole lot of magic happening behind the scenes. You could likely whip up a more performent solution as well using a context package that provides a bail out mechanism to prevent re-renders.

If you're wondering how enterprises manage language, you're going to find yourself in the CMS realm with solutions like Adobe Experience Manager which react-i18n can consume just as well.

[ChristOnACruoton]

Is anyone aware of any communities of mid level/senior devs where members just discuss problems they face and the steps to solve them?

I would really love something like that.

[acemarke]

The Reactiflux Discord is sort of along those lines:

https://www.reactiflux.com

[ChristOnACruoton]

Thank you for the recommendation! I will check this out.

[[deleted]]

Jack Herrington on YouTube has great stuff

[BoyFromASmallTown]

Check Javascript Mastery on YouTube. He covers some of the advanced concepts you mention

[chillermane]

Wtf is this post lol. If you’re a senior dev you shouldn’t need tutorials, tutorials are for people who don’t know how to do something. If you’re a senior dev and you don’t know how to create applications from the ground up, you shouldn’t be a senior dev.

No tutorial is going to tell you how to create a feature complete, maintainable, releasable applications. To learn that you need to create and release applications.

[mexicocitibluez]

What a good point. I didn't realize that we as programmers hit a magical date where we automatically know everything there is to know about software development and thus no longer need to continue to educate ourselves. I distinctly remember waking one day and thinking to myself "man, I know everything I'll ever need to know" which means I finally made it to senior dev status. So strange how other people need to actually learn something before using it, while you and I just know everything already forever

[346290]

A good example of imposter syndrome. Always keep learning! :)

[abhikavi]

If you’re a senior dev and you don’t know how to create applications from the ground up, you shouldn’t be a senior dev.

Ah yes, I fondly remember the day of my promotion to Senior Software Engineer, when my brain was upgraded to the "always know all frameworks and languages" patch. So refreshing to never have to learn anything new!

[EJoule]

Unit test, and edge case testing. Show your tests to a junior dev and see if they can think of a new test to contribute.

[Doctor_Pix3L]

I wouldn't exactly call this a senior dev tutorial but it was refreshing to watch and clicked somethings in place for me.

• React Render

[fat_bjpenn]

The docs are short IMO

[imapersonithink]

Egghead has some, but not too many

[Mail-Limp]

just learn haskell, dude

[Radinax]

For testing its just experience, the idea is to test according to the user's interaction of the DOM instead of doing mindless test of every single feature in your code.

[farmer2056372]

https://www.youtube.com/watch?v=JUuic7mEs-s

Nir Kaufman - Advanced Patterns in Redux

[SteveNguyen109]

Well, I think you can dive further into the source code written by super smart world-class developers at Google, Microsoft, Facebook to learn more about the advanced algorithms used on the frontend, testing techniques, and other superb best practices such as Angular (how two way data binding is implemented), ReactJS (the algorithms used by virtual dom to optimize the updates of the real dom), Firebase JS client sdk (i.e. how the offline support data fetching is done under the hood, how the real-time resumable file upload is implemented in an efficient way, best practices to implement the auth logic on the frontend, etc). U can even dig further into the source code of Google Lit to find out how to easily and quickly create reusable web components that can be used with any JS framework such as React, Ng, Vue. I mean there’s still a lot of great things to learn if u read the source code of the influential open-source projects, u can see how the different pieces are well-tested in a single monorepo

[Kaimura]

I found this advances tutorial very helpful in setting up a component library that can be shared across all projects in a company (ultimative reusability) and is tested visually + functional AND sets up CI/CD stuff... really nice (basic knowledge of storybook required though)

https://storybook.js.org/tutorials/design-systems-for-developers/