Software Developer who works mostly on Web stuff. I like JS, but I also like other things. I also do photography, and look at sneakers online that I will never be able to buy.
Ms. Lee: How has dev.to changed in the last couple of months? What kind of workload does the PBJ have in these days with the increased userbase?
Also, what is the reasoning behind open sourcing dev.to? What does the company hope to/expect will happen when the codebase goes open source? Looking forward to learning how dev.to was built!
Let's see...well, we started doing AMAs 😛, but feature-wise we've added: reactions to articles (the unicorn reaction is up for interpretation!), notifications, a smarter home feed, and the ability for organizations to self-create their own accounts (we used to have to do that manually). Oh! And the #hiring board.
We're in a unique position where the community has the ability to build itself. When we open source, we hope people will jump in and start building out enhancements they want to see. We can make dev.to more robust, very quickly. We're also excited for our codebase to generally improve because we'll have more eyes on it keeping everyone accountable. We come from the belief that sharing work is what's best for the world and open source software is always the best software, so that's where we want to be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ms. Lee: How has dev.to changed in the last couple of months? What kind of workload does the PBJ have in these days with the increased userbase?
Also, what is the reasoning behind open sourcing dev.to? What does the company hope to/expect will happen when the codebase goes open source? Looking forward to learning how dev.to was built!
Also also, thank you for the must-read emails!
Let's see...well, we started doing AMAs 😛, but feature-wise we've added: reactions to articles (the unicorn reaction is up for interpretation!), notifications, a smarter home feed, and the ability for organizations to self-create their own accounts (we used to have to do that manually). Oh! And the #hiring board.
We're in a unique position where the community has the ability to build itself. When we open source, we hope people will jump in and start building out enhancements they want to see. We can make dev.to more robust, very quickly. We're also excited for our codebase to generally improve because we'll have more eyes on it keeping everyone accountable. We come from the belief that sharing work is what's best for the world and open source software is always the best software, so that's where we want to be.