So word is getting out the MDG dev team is changing. I have not seen any details about why but I am starting to see past employees change their job history on LinkedIn, Twitter and personal sites. It would be helpful for us to get an official statement from MDG before it turns into a gossip storm.
I did not start this post correctly. This better communicates my thoughts:
I have noticed there have been changes to the MDG team members. I have heard a number of developers have left or asked to leave. I know the MDG team works insanely hard at what they do. We see MDG team members as a older sibling of sorts. Just like when we celebrate a new team member hire, I think a company and community should honor someone for their contributions when they leave.
I am asking MDG leadership to recognize those who left so we all could thank them for their contributions over the years. Meteor would not be what it is without their contributions.
I think people leave, teams churn. Only thing we can do is wish them well and get back to our lives. I don’t think they even need to address this. It’s not like this a professional sports team that needs to answer to the media.
Actually with the state of flux Meteor is in, it would help people new to the platform know if choosing Meteor was a good idea or not. It’s not like there is a huge need for Meteor developers, just Meteor hobbyists. Less then 300 results for the entire US when searching for Meteor jobs on Indeed. When you peruse forums, twitter and reddit, the overwhelming response is that Meteor is a gimmick. Rails continues to churn forward, stable and transparent.
Once you’ve decided to use JS, now you have a ton of choices to make - which view layer? How do you do data? Etc. etc. Meteor is one of the choices you can make in JS and it does for you. But you can always use other parts of the JS world.
Pretty sure you misunderstood what I said. I wasn’t asking about choosing Rails, I was pointing out the fact that their development, current and future is very transparent. DHH is very vocal about the platform and you know what you’re getting when you get involved in that ecosystem. The same can’t be said for Meteor, as of right now.
It’s not about momentum, because we’re not talking about JS here, we’re talking about Meteor. JS has the momentum, but does Meteor?
The point being, with the number of changes to Meteors future and the recent departures from the MDG, some transparency from the group would be appreciated by the people who want to embrace the platform, but just aren’t so sure it’s a great decision.
I’m pretty confident that any past and future changes are bringing MDG towards being a more open and collaborative platform - we’re working our butts off to have a more open design process, bring in more contributors, handle GitHub issues and pull requests better, and integrate with the wider community wherever possible. I think many of our actions in the past months show clear steps in that direction, and I anticipate still more movement in the near future.
Perhaps I’m biased as I look at this (Meteor) as a project that I’d have to answer for. When moving forward, every dev or team has to balance things like testing, documentation, community, and actual development. If a client demanded complete transparency about every decision made by a dev team, how would that affect productivity?
Also, comparing Rails (b. 2004-5) and Meteor (b. 2011) and assuming they are/should be in the same cycle/state of dev seems like a cheap shot to me.
Its funny how people in these forums put words in others mouths to defend their position. Nobody brought up comparing features, state of development, etc. The only point, and the only one that matters, is transparency. This isn’t a client/developer relationship, so you’re deflecting there. The point is, and remains, that the MDG needs to do a better job being transparent about the state of Meteor and not expecting people to just ride it out with them because they’re good at giving vague answers. Sorry, but thats the feeling towards the MDG OUTSIDE of this forum.
Whats the roadmap for development? What are some hard dates to look forward to? What’s your anticipated feature set for 2016? Where are you moving with Blaze? How focused in NPM integration. Some of us have to hard sell our solutions to employers and when working within a team, you need to have solid answers to back up your position. Right now, its a bunch of “well, maybe, we’ll see, we’re trying, we expect, we anticipate, etc.”
Be straight forward with your community or you might lose it.
I have two full time clients, both large projects in Meteor, a platform I suggested in both cases. So I feel your pain when you’re asked the tough questions about Meteor and you have to worry about perception with investors, etc. Still, I believe it was a good choice in both instances, and just have to move forward.
That being said, I’m not trying to defend a position or a person or a company; I enjoy a good discussion as much as the next. If my analogy was interpreted as deflection, then it was misinterpreted. I was merely trying to relate a common scenario amongst devs.
If you want to look at Meteor as a standalone project, implying that it is a gimmick based on reddit/twitter and comparing it to Rails isn’t the best strategy in my opinion.
I will agree that the transparency could be improved, but I think things like Transmission, more communication on the forum, the blog, etc. are an effort to move things in the right direction.
Thanks for the wishes After almost 4 years at Meteor, I felt like it was time for something new. 4 years in startup land is a lot! I’ve changed courses in my life every few years since I remember myself, this is no different.
And I agree with @abhiaiyer – people move jobs all the time, especially in Silicon Valley.
@avital thank you for all the years of hard work you put into Meteor. Truly amazing. 4 years is a lot, I was just reading how the average dev employment length is 19 months in the Valley. I wish you great success in the AI world, it is certainly very exciting times!
I framed the post wrong. What I meant… The MDG team works insanely hard at what they do. We see MDG team members as a older sibling of sorts. Just like when we celebrate a new team member hire, I think a company and community should honor someone for their contributions when they leave. If there is no recognition of them leaving then there is no opportunity to thank them and wish them the best (like you said above).
So I guess I was calling out MDG and asking them to recognize those who left (more than just Avital) so we all could thank them for their contributions over the years. Meteor would not be what it is without them.
Agreed. People just leave every now and then. I used to do the same. It’s not always about the company either. Besides, at my current startup, which I’m looking at with a fairly objective opinion (since I’m more like a guy who can leave at any time once our own startup makes enough revenue so I’m not too “invested”) can say that people leave here very fast. We’re happy if we can keep some people longer than a year, which is mind boggling because I’ve never worked in such a great environment before my whole life. It’s not always in control of the company if people leave. They just do, doesn’t have to be related to the company.
Perhaps in the USA it’s not culturally normal but here in the Philippines for example it’s a fairly common thing for employees to switch fairly often (sadly).
As with all jobs there’s an important work/life balance to maintain. I get the feeling that, as @benstr says, people at MDG “work insanely hard” (I’m fairly certain @sashko’s been cloned, given what he puts in). No matter how much you may enjoy working anywhere, it’s easy to become burned out when the pace is hard. Sometimes moving on is the right thing to do for all.
Anyway, thanks to everyone, past and present, who’s helped make MDG and Meteor awesome.