Location: New York, NY
Remote: Ok
Willing to relocate: Not at the moment
Résumé/CV: Upon request
Over a decade of experience building digital products. I’m a juror at The FWA and also had experience as an instructor for React's Nanodegree program for Udacity.
I’m available for part-time freelance work; project-based or mentorship/consultancy opportunities.
Some of my recent client work features Apple, Epic Games, Oscar Health and T‑Mobile.
Technology I use the most these days are React/React Native, Electron, TypeScript, GraphQL, Node.js and AWS. I also have experience with Clojure and am very interested in distributed systems.
Email, GitHub and more information available on my website: https://rinaldi.io
Over a decade of experience building digital products. I’m a juror at The FWA and also had experience as a teacher for React's Nanodegree program for Udacity.
I’m available for part-time freelance work; project-based or mentorship/consultancy opportunities.
Some of my recent client work features Apple, Epic Games, Oscar Health and T‑Mobile.
Technology I use the most these days are React/React Native, Electron, TypeScript, GraphQL, Node.js and AWS.
I also have experience with Clojure and am very interested in distributed systems.
Email, GitHub and more information available on my website: https://rinaldi.io
I've added Codepen's MIT License [0] to your name to credit you correctly at the right spot on our CSS. New build will be rolled out in a couple of hours so kindly check back again.
If however you're still uncomfortable about us using this experiment without a coffee, do let me know and we'll remove it from Bubblin completely. Just kidding, we'll sponsor you a coffee as well ;-)
I don’t get the _fear_ of releasing the 1st version of a library at `1.0.0` and then doing major bumps whenever needed. That’s why semver exists in the 1st place.
There seems to be a lot of FUD around this subject.
I would love to know what the reasonable approach would be ideal from the people talking bad things about GitHub. If they responded to issues right away people would complain too.
It's not easy to come up with a solid plan for new features and improvements, specially in a company this big (that has a lot going on as we all know).
What? You think they're going to get that list of complaints and start smashing some code? That letter is not even 1 month old.
I can kinda understand the frustration but keep in mind that there's a lot of other things to handle, it's more complicated than that.
In the meantime if you're really struggling, there are other great options available out there like BitBucket and GitLab.
I would love to know what the reasonable approach would be ideal from the people talking bad things about GitHub.
Treat their software development savvy usebase as stakeholders in their ongoing project rather than unwashed masses consuming a loss leader?
A mutually-agreeable reasonable approach probably doesn't exist. Limited visibility into the project may be considered exposing too much of the business for GitHub's tastes. So it will continue to be a one-way relationship, with all the baggage that comes with a one-way relationship (incl "talking bad things").
Well they used to be open about their future plans on their blog[1].
It hasn't been even a month after that letter and we _finally_ have a response from them. It really doesn't seem to be that big of a deal IMO.
A reasonable approach? When I'm in doubt, I just go with the truth. They could have said "Hey, we hear you, we're starting a group to figure out how best to resolve your issues." or "Hey, we've already been working on this, we'll get back to you in a couple of months." Or even a "Hey, we get you aren't completely happy, but we just don't have the time to address your concerns right no, but when we can, we will."
Any of those would have been better than perfect silence followed with, we'll see what we can do.
I’m available for part-time freelance work; project-based or mentorship/consultancy opportunities.
Some of my recent client work features Apple, Epic Games, Oscar Health and T‑Mobile.
Technology I use the most these days are React/React Native, Electron, TypeScript, GraphQL, Node.js and AWS. I also have experience with Clojure and am very interested in distributed systems.
Email, GitHub and more information available on my website: https://rinaldi.io