I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I think it's a good idea, but I have a few comments.
First off, I know it's early days, but it's unclear from the site whether it's about:
specifically creating events in the name of dev.to
organising other events and listing them if they may be of interest to dev.to members
cataloguing externally-organised events that may be of interest to dev.to members
something related to development in general but not specificaly dev.to
We have existing projects sharing open data, like open tech calendar for example. Is there likely to be data fed to and from dev.irl in some standard(ish) way that other services supply or consume, or is it going to be about members curating their own events?
What's the purpose of it being on a separate URL? That adds to my confusion, as a naive visitor, as to whether it's intended to be a separate entity.
The word "dev" is very general, and (like you can see with things like the comments on the D&D alignment tweet from a few days ago) it doesn't have the recognition of names like Reddit or SO, which might muddy the waters a little if people think it's a generic site when it's actually tied.
Is it going to be fed back into the main dev.to site as part of people's feeds?
I think this is all valid feedback and we'll try to take it all into account.
specifically creating events in the name of dev.to
This is the closest to what we intend. Less in the name of but more for those people specifically involved in our community. We will have more tie in with dev.to itself as we flesh this out but we felt like standing up a new website would help this initiative have its own special kind of weight which wouldn't be hampered by needing to fit it into the main product right now. We will be looking to create more interesting integrations as we make these work but have to start somewhere and we didn't want to be too top heavy.
The choice of the other domain is as much an experiment as anything. If we are able to create an ecosystem of fun, healthy events one way or another we have accomplished the goal. In terms of the difficulties with DEV, dev.to and naming this thing in general we're still trying to find the right answers there.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I think it's a good idea, but I have a few comments.
First off, I know it's early days, but it's unclear from the site whether it's about:
We have existing projects sharing open data, like open tech calendar for example. Is there likely to be data fed to and from dev.irl in some standard(ish) way that other services supply or consume, or is it going to be about members curating their own events?
What's the purpose of it being on a separate URL? That adds to my confusion, as a naive visitor, as to whether it's intended to be a separate entity.
The word "dev" is very general, and (like you can see with things like the comments on the D&D alignment tweet from a few days ago) it doesn't have the recognition of names like Reddit or SO, which might muddy the waters a little if people think it's a generic site when it's actually tied.
Is it going to be fed back into the main dev.to site as part of people's feeds?
I think this is all valid feedback and we'll try to take it all into account.
This is the closest to what we intend. Less in the name of but more for those people specifically involved in our community. We will have more tie in with dev.to itself as we flesh this out but we felt like standing up a new website would help this initiative have its own special kind of weight which wouldn't be hampered by needing to fit it into the main product right now. We will be looking to create more interesting integrations as we make these work but have to start somewhere and we didn't want to be too top heavy.
The choice of the other domain is as much an experiment as anything. If we are able to create an ecosystem of fun, healthy events one way or another we have accomplished the goal. In terms of the difficulties with DEV, dev.to and naming this thing in general we're still trying to find the right answers there.
I think it's going to be cool.