I got introduced to HTML through Neopets as well. I remember joining a Legend of Zelda guild. Another member and I decided to start our own guild. He showed me how to use an image tag so we hotlinked a bunch of sweet images and created a bunch of new accounts to boost our member count and that helped us organically get members. Good times!
On AWS, we bake our AMIs with packer and include the Ansible roles and playbooks.
We use CloudFormation to deploy, so in the instance metadata we have it run Ansible locally to bootstrap and return the exit status to cfn-signal.
We retrieve secrets via Parameter Store. For environment specific configs that are not secrets (ie passing in vars from CloudFormation), we have cloud-init write a json file that we include with our ansible-playbook command.
Agreed, the logistics company IKEA uses - North American Logistics Group is the worst.
A table top got damaged so they had to get me a new one and they said I should call them to reschedule. It was impossible to reach anyone. Even talking to IKEA CS on the phone was clueless as to what to do.
I finally just sent a DM to IKEA customer service on Twitter and they got everything sorted out. So if you need help just message them on Twitter.
Perhaps you could instead pivot this idea. I think it would be more interesting if you could have the editor play back all the actions taken that led to the resulting commit.
That'd be pretty cool actually. I write quite a bit of Ansible, and having someone to talk to about Python could be really useful. I'm a ruby/js guy myself and have started writing react-primer-draft on github. Feel free to reach out via my email in my profile.
Because people can be very opinionated. You're obviously going to find very vocal people on the internet.
They may be pushing you toward a technology because that's where they found their happy path. Could also be a way for them to justify their own choices.
At the end of the day, just pick something and build it.
It's not really that SPA specific, if you want to just use React for the View, then Part 1 and Part 4 (to be written) is probably all you need to get started.
Collectively, all the parts of the primer, together should give you the tools you need if you want to build a SPA.
At the rate I am going, I am hoping by next week. But, the author of Alt has already written an amazing getting started guide: http://goatslacker.github.io/alt/guide/ - check it out!
As for a contrast between Alt/Reflux, I am hoping others using different Flux libraries will contribute and share their views, I will also link to some comparisons others have already done, such as: http://pixelhunter.me/post/110248593059/flux-solutions-compa.... But if I have time to, I'll give it a try!
I am also struggling with whether it is time for me to move or not. But I think your point about only learning from people better than you... that is a interesting perspective.
Like the OP, I think we consider ourselves to be at the "hyper-growth-learning phase", where we can really accelerate our potential by working with really talented people. But yeah, eventually you're going to be that "Senior Developer," and it'll be up to you to continue improving and helping others improve.
I've only been in the industry for 2 years as well.
Right now, I feel like I'm the only person on my team that is continually self-improving and trying out new things. It's always me bringing back new things and sharing with the team. Sometimes, I feel like I could benefit way more - like 2-3x - if I was on a team where everyone was self-improving and we could just all feed off that energy.
I have an extraordinary amount of autonomy. My year end review only consisted of, how I knocked everything out of the park and something along the lines of helping get into more of a leadership role.
Sometimes, I think - am I doing so well because everyone around me is just average?
Do I wait around to be promoted into leadership? I mean I've done fine self-learning and keeping myself up to date. But honestly, I think would hate to end up being in some sort of leadership position just because I've been with the company for a long time and have delivered consistent results, and then end up with mediocre tech skills.
Or do I say its time to part ways and focus on becoming a really good engineer and join a team that can continue to accelerate my skills?
For me, I am leaning toward the latter. When I feel I hit that "Senior Developer" phase, that's where I'll re-evaluate where I want to go next.