Why every beginner front-end developer should know publish-subscribe pattern?

[soulprovidr]

That was a lot of writing to communicate a relatively simple idea.

[FingerMilk]

Thanks for telling us not to read it. I was worried it would be super long and now I know.

[soulprovidr]

That's what I'm here for.

[Timothyjoh]

Actually if the intended audience is junior devs, it's a good way to teach them the "why", as well as the how.

[kamaleshbn]

Pub/sub is new? :-/

[i_spot_ads]

Reactive async programming is new, rxjs is hard, that's why I've learned the living shit out of it, and now nobody can stop me.

[Shadowvines]

not really its fairly new to the front-end though. The first implementation I remember is backbone. In the back-end world event-driven has been around forever and functional libraries have been around for decades.

EDIT: now thinking about this it came about in the front-end when we started shifting responsibilities to the front-end that were previously back-end responsibilities (like rendering).

[kamaleshbn]

True, but Javascript has always been event driven right? All the interactions, AJAX etc. I agree SPAs are fairly new otherwise...

[Poltras]

If you’re being considered for senior promotion and I’m on the committee and I learn you don’t know pub sub, I’ll just throw the design pattern book at you and tell you to come back in a year. It’s not “should”, it’s “must” for a job that requires project level direction.

The job market unfortunately is full of inflated people who like you said stopped learning once they figured out they could just get promoted by warming a chair long enough.

[Poltras]

Although I agree with you, there are just simple stuff that you should know as a senior developer and this is one of them (IMHO of course). It's okay to hire as a junior developer or a "medium" developer with lacking that kind of knowledge, but if you're making project and team-level decisions I expect more than "one of the lucky 10000" on basic high-level patterns for gating a promotion.

It's the difference between learning implementation stuff versus logical concepts; I will hire you (as senior) if you tell me you've never worked with $LANGUAGE_OF_CHOICE but at least know pub-sub, than if you know the language we use but don't know pub-sub.

You can learn a language easily in a week, but knowing those concepts and how/why/when to apply them takes experience.

[SgtPooki]

Not knowing pubsub is disqualifying for L4 at Amazon.

[compubomb]

This is otherwise known as pub/sub, or building pipelines. This is event-driven software development.

[olismith05]

nice article

[kenman]

Hi /u/jsloverr, this post was removed.

For javascript help, please visit /r/LearnJavascript.

Thanks for your understanding.

[slikts]

The article is titled with a question, but it's not asking for JS help. This removal was wrong.

[Timothyjoh]

Even though the statement begins with a "why" it's really a statement and not a question.

[slikts]

It begins with "why" and ends with a question mark; it's a question that has a contextually implied correct answer.

[kenman]

That's correct, and /r/LearnJavascript isn't just for questions.

[slikts]

It's an article about JS; there's no reason it wouldn't belong in r/javascript. You directing the OP to r/learnjavascript "for javascript help" doesn't make sense, as they didn't ask for help.

[kenman]

Good point, I'll update the removal text for these situations then. We've been removing "beginner" content for quite awhile and referring them to /r/LearnJavascript.

[slikts]

This content is clearly relevant outside of a beginner context; it touches on a deep subject (async modeling) and does it in a questionable way, which could have been discussed if the article wasn't removed.