Since last week, I’ve been wrapping my mind around APIs as I head toward the building phase. I also had the opportunity to join my colleagues at the All Things Open conference in Raleigh, celebrating our shared enthusiasm for open source and hearing from speakers of all disciplines. Per usual, some speakers were more engaging than others, but it was very cool to attend such a wide variety of talks — from UI/UX/Design to Front-End to Back-End.

It was interesting to get introductions to what is to come — Angular 2.0, ES6, modular Sass, and more. Some talks went straight over my head, but delivery is key. It’s a challenge to be both engaging and informative on some of these topics and some talks were evidence of that. Most were more intermediate level rather than introductory, but I received some good resources to look into further. With technology always changing and growing — new versions of software, languages, frameworks, libraries releasing all the time — how does a company or individual decide “ok, now I’m going to learn this new thing”? I guess it depends on how progressive they are, how flexible and open to change.

It can be a pain to make the change — time spent learning the new bells and whistles, the possibility of it not being that great after all, having tons of bugs or creating problems because of other tools in use. There’s a lot of risk in making the shift, so I suppose it makes sense large companies are much slower at making the move.

So much of programming involves learning things the hard way. I’m in luck; my stubborn nature means that’s the way I learn everything. It’s interesting to reflect on this whole process of creating (what should be) useful things, that sometimes aren’t, but to keep trying anyway.

“It’s not that I’m so smart, it’s just that I stay with problems longer.”
– Albert Einstein
Like what you read? Give Lindsey a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.