jamier1978

When this article was published on his altdev blog it had a big impact on how I wrote code. I really embraced pure functions and tried to think in terms of side effect free code and inputs/outputs.

Got no real data for it but I felt the quality of the code I wrote was much better going forward.

"an uneven worker" sums me up nicely.

As someone who worked with Delphi for many years I've often wondered if there is a lot of money to be made by charging companies to work on these codebases. As much as I liked Delphi back in the day, low job satisfaction puts me off looking in to the idea.

Also the compiler was lightening fast.

A significant amount of Delphi code I wrote 20+ years ago is still in the wild and still making a ton of money for a company I used to work for.

I actually miss the days of Windows desktop development. Good Times.

To me the two bits of code in the error handling case or not comparable. In the c++ case you would still handle the error in the if statement if it can be handled otherwise you would throw it. C++ has the advantages of giving you both options.

There isn't many people who could hold my attention for 5 hours but John is one who can. Speaks so well about his craft.

As a someone living in the UK I find a lot of these comments by people in the US mind blowing. People calling CPS / police because they see kids playing alone in the park? What the hell is going on over there!

True. I found this quote kind of sad "What I find is I'm able to be with them and still be on email. I can be with them and still be working at the same time ... If I didn't, I wouldn't be able to get my job done."

I don't know how much time he actually spends with his kids, but I suppose its comes with the territory of trying to change the world.

Didn't know he has 5 kids! I struggle with 1 full time job and 2 kids.

That's good to know. React Router is the only thing stopping me from updating to React 16. I can't find an NPM package, so assume you need to point it at Github?

I have to say this near perfectly mirrors my experience. We have a JS application [1] that is getting fairly large in size and development is moving quickly. Before we introduced React + a Redux style pattern (we don't actually use the libraries but have borrowed heavily from the pattern) we did find it difficult to track down bugs and making changes to existing features became a minefield.

I feel the pattern has helped as the team has grown. Yes there is boiler plate, but that boilerplate makes it hard to deviate from the pattern e.g. if you want to update the application state, you must dispatch an action, no way around it. In the past with MVC/MVP style patterns responsibility get muddled and you get a lot of inconsistency in implementation.

I've got no data for it, just observations, but since we have switched a to more functional style of programming and using immutable data, we are encountering less bugs which I put down to side effect free code.

Overall we have had a positive experience with React + the Redux pattern. Yes you could do this with other frameworks and patterns, but it works well for us and no doubt the same argument could be applied to whatever framework others are currently using.

[1] www.barvas.com

We are in the same position, except with backbone instead of spine. Nice idea for a use case of portals.

same here. Really good to see these types of updates going in along with the bigger things like fiber

According to the FAQ they will be shutting down the Stormpath API in 6 months. https://stormpath.com/oktaplusstormpath

FAQ also says you will need to export your data from SP and, presumably, manually import it in to Okta. If thats the case its going to be hard to do it without end user disruption.