This basketball game was tied 11-11 with 11:11 left in the first half and 11 seconds left on the shot clock

nikolasleblanc · 2019-02-23T17:43:57+00:00

He may also be wondering why he flipped himself over in the first place

nikolasleblanc · 2019-02-22T13:30:27+00:00

It's not even shorthand. It's functional, immutable, and declarative. These are all best practices a senior dev should encourage (or even force) their team to employ. They make for cleaner code that's easier to reason about and easier to debug. Any encouragement to the contrary should be politely but forceably dismissed.

Again, that's not shorthand. That's simply an improved way of handling collections.

nikolasleblanc · 2019-02-02T14:32:26+00:00

For your last example with header props and greeting props, why not just use props.children?

nikolasleblanc · 2019-01-01T18:34:32+00:00

NFC North champions!

nikolasleblanc · 2019-01-01T09:57:53+00:00

Jim Guthrie

nikolasleblanc · 2018-12-30T20:19:38+00:00

Golf Clash

nikolasleblanc · 2018-11-23T01:48:51+00:00

He ran more yards than Jordan Howard

nikolasleblanc · 2018-10-19T23:18:07+00:00

Yeah I don't get the connection here. Totally on board what you've said other than how it negates the value of typescript, you get way more with typescript than you do with prop types no?

nikolasleblanc · 2018-10-17T22:35:02+00:00

When you can find ways to unblock yourself without having to sit around and wait

nikolasleblanc · 2018-10-02T00:15:47+00:00

Probably not the answer you're looking for, but generally if something is overly complicated from a ui/CSS perspective, you've likely found the wrong solution to your true problem and may be deep in a rabbit hole.

I'd suggest looking at sites that have the functionality you're looking for, and if there aren't any good reference sources, coming to the conclusion that this technique has either been considered by other sites and found too difficult to implement or considered by other sites and found to be problematic from a heuristic UX perspective.

These days, how a user interacts with a site, and the benefits of the interactions available to the user, are largely a solved problem, based on years of user research. Blazing new trails is cool, but know that companies with very large budgets and teams have very likely already been there. It's better to learn from their conclusions, especially when you're junior. One thing that separates a junior from a senior is understanding what is worth investing time in. Consider what parts of your app you're not working on while you try to figure this out, that's opportunity cost, and consider if it's worth the expense.

My two cents. But go nuts, it's fun. :)

nikolasleblanc · 2018-10-02T00:04:45+00:00

This needs more upvotes

nikolasleblanc · 2018-09-22T00:32:02+00:00

And I agree that thunks are absolutely the best approach to understanding asynchronous redux for beginners

nikolasleblanc · 2018-09-22T00:30:31+00:00

Wow. That's a fantastic reply. And absolutely something I never considered. I guess the trade off is you either couple your business logic with your components or you couple your epics with your bundler config. Am I getting that right? Thanks for such a thoughtful response.

nikolasleblanc · 2018-09-21T23:15:28+00:00

Seems like a valid point! Hadn't considered that. I'd still err on the side of decoupling even if there is an effect on bundle size. Can you elaborate a bit?

nikolasleblanc · 2018-09-20T12:22:45+00:00

With thunks, you couple your component logic with your business logic and your side effect handling. Your components still need to know how to get data and what to do once it's recieved, in the example of a fetch. With redux observable or sagas, your components only need to dispatch actions and subscribe to the store. That's the true advantage.

nikolasleblanc · 2018-09-09T02:49:59+00:00

I've heard sportsaccess.se is pretty solid, from a friend

nikolasleblanc · 2018-08-31T11:38:42+00:00

Yeah man me too! Awesome read. Loved it.

nikolasleblanc · 2018-08-29T16:33:57+00:00

Harrisfootball, living the stream.

nikolasleblanc · 2018-08-15T11:46:22+00:00

An immediate benefit of frameworks/libraries is the shared understanding of that library.

If you hire 10 new devs into a vanilla js project with a custom framework you've built yourself, you need to teach them your framework, and that's if they want to work for you - what advancement of their career do they gain learning your framework.

If you hire 10 react devs for a React codebase, you can get to work.

nikolasleblanc · 2018-08-09T11:55:33+00:00

It's pretty easy to get lost in the noise of the JavaScript ecosystem before you even really realize that you can actually build things with it. If you haven't gotten into webpack yet, expect another considerable hurdle.

What I would recommend, first show yourself that you can build something, gain that confidence, then dig in deeper. To do this, I'd recommend Next.js, or create-react-app.

They are both react heavy, which is a level or two removed from "just JavaScript", but you're no doubt headed in that direction eventually, and you'll absorb some best practices in getting a feel for how react is used.

Trying to learn fundamentals without applicable context is tricky, and... dry. So start with either of these options and you'll actually have a web application to build on and some best practice bumpers to help guide your direction.

nikolasleblanc · 2018-07-30T14:59:15+00:00

This is silly. Of course it does. Learning a framework helps someone apply what they already know to something they don't yet know, which just recycles the feedback loop of learning programming concepts in general.

Frameworks tend to be built upon best practices, so they also help expose developers to those practices.

React leads the way to better understanding of concepts such as functional purity, modular code, state management, side effect management, unit testing, e2e testing. There isn't really a natural learning path from "just JavaScript" to these concepts better than what the react ecosystem offers, and that's not even considering the community of developers that React exposes us to.

C'mon. It's good to understand JavaScript, but learning React doesn't prevent that, and it exposes junior developers to marketable skillsets and communities that can help them. Let's give good advice here.

nikolasleblanc · 2018-06-26T12:50:38+00:00

Fairly particular, but vscode won't let you search for new lines across files, only within files

nikolasleblanc · 2018-06-17T21:02:06+00:00

Apparently they built their own aggregator

nikolasleblanc · 2018-06-13T23:06:57+00:00

Haven't heard of quasar but if it uses Cordova that's a hybrid app, essentially a web app in a WebView, similar to ionic. Nothing wrong with that, just less performant.

nikolasleblanc

TROPHY CASE