As we work every day on this community, it’s hard not to be overwhelmed with feelings of thankfulness. We get to come in to work on making the software community feel a bit more like a community day in and day out. This work is a privilege gifted to us by a community of teachers, sharers, and believers.
Any growth of this project was never a given. Every week is a new chicken and egg problem and many unanswered questions. We rely tremendously on the shared belief of the community that we were on the right track. It has helped us overcome many bugs, missing features, and inconsistent experiences along the way. We were always propped up by the many fairy godmothers that make up this wonderful space.
We’re not the first company to try this sort of thing and we won’t be the last. But if we are going to keep growing and keep doing new things, it’s going be for the same reasons we’ve gotten this far
As builders and administrators of this place, there’s always a small fire that needs to be put out. The lifeblood of this community is that people are so darn willing to share and teach and be awesome, and it just keeps happening. It’s like some kind of magic.
Take this thread from earlier this week for example:
Holy cow! Can you imagine what a critical moment this could be if you’re a newer dev floating in a sea of uncertainty.
Or this post from the previous week:
They don’t teach the endless nuances of web security in class. That class would be 100 years long if they tried. But with the right informative posts popping into our worlds at the right moments, we make it work.
What about this:
The documentation out of context or narrative is not always useful in solving problems we’re not currently in the midst of dealing with. It’s hard to Google for “things I don’t know I don’t know”.
And for more depth and narrative context, the community consistently comes through:
And sometimes we need just a bit more guidance through the nuances:
Sometimes you need a concept explained simply:
And sometimes you just need ideas:
Sometimes we hit a bump in the road and need the community to pick us up:
And when we have a moment of success, we need to share:
And share some more:
And some more:
Sometimes we need to change our Twitter names to stylized unicode characters 𝖑𝖎𝖐𝖊 𝖙𝖍𝖎𝖘 for no particular reason.
Sometimes we need the leaders in our space to tell us they’re human too:
And sometimes we need them to explain experimental browser APIs we didn’t know existed:
And sometimes we just need them to be open with us:
Sometimes we need to be updated when a library has new goodies:
And sometimes we just need to know where to put things:
Sometimes we need to know we have options in our career:
And sometimes we need to discover the mistakes we need to avoid:
Sometimes we really need to discover the mistakes we need to avoid:
And then there are those who help see the community as a tool for individual progress:
Sometimes we get to share in the building this place with everyone:
And sometimes that results in amazing progress:
Sometimes they write the posts that the core team never got around to writing:
Sometimes it's hard not to be amazed at what the next year might bring. Thank you to everyone helping to make the software development career a bit better for everyone.
This series of posts document a high-level process to use when planning a modern web application, from project organization, collaboration considerations and tooling choices during development, all the way through deployment and performance strategies.