David Rosenstrach and I
Hey Guys,
Myself and a few other guys spent some time last week flushing out an idea for what I call “Tech Dinner Salon.” – Basically a self-organizing forum for people to discuss these types of issues. Among the top ideas for discussion was exactly this – how to foster more tech in NY.
I haven’t posted it to the larger NextNY list, but would love your feedback.
http://www.nextny.org/wiki/show/Tech+Dinner+Salon
http://www.nextny.org/wiki/show/DinnerSalonSignup
Thanks,
Jean
Agreed - we need to involve all of these. (I wrote nearly the same list
to Hank in a private email a week or 2 back.)
If I could elaborate a bit more on the list though:
* re: #4: there's a couple of University sub-constituencies, and we
might want to try to include all of them: 1) "technology transfer"
divisions, who are concerned with licensing university research to the
external tech community, 2) university tech students, who are concerned
with finding tech jobs when they finish school, and 3) university tech
professors/department heads, who have some of the same concerns as the
students, but also have some interest in tailoring their curriculum to
suit the market's needs.
* One really important constituency that was omitted from this list:
city government. e.g., ITAC, or a rep. from the Mayor's office, etc.
> Interested to hear how people think we can make progress toward
> increasing New York's importance as a tech center. Certainly this is a
> tremendous opportunity.
>
> Eric Wiesen
My personal opinion is that the first thing we ought to do is to get a
representative from each of those constituencies to chime in and vent
about why, from their perspective, the current situation sucks, and
(hopefully) some suggestions on what could/should be changed to make
things *not* suck. Having a list of those would IMO give us a pretty
clear picture on what exactly the problems are, and who's being affected
and how.
Then with those in hand, we can then be in a position to really
understand the problems, the causes, what's the highest priority issues,
etc. We could then consolidate those issues into a master list of
objectives for the effort, and an action plan on how to achieve them.
I'd be happy to volunteer to write up the list of developer/engineer issues.
That said, Hank disagreed with this approach a bit. (Again in a private
email exchange we had; glad we'll have a public forum for this stuff
from now on.) I hope I'm presenting his opinion correctly (and please
feel free to correct me if I'm not, Hank), but he thought it'd be better
to get a non-profit together for this, get some funding for it, and hire
some people to do a more professional analysis of the problem.
Your thoughts?
DR
That said, Hank disagreed with this approach a bit.
(Again in a private
email exchange we had; glad we'll have a public forum for this stuff
from now on.) I hope I'm presenting his opinion correctly (and please
feel free to correct me if I'm not, Hank),
but he thought it'd be better
to get a non-profit together for this, get some funding for it, and hire
some people to do a more professional analysis of the problem.
Well, sounds like we're basically on the same page. I also agree that
the effort will need to grow beyond an all volunteer force. (Indeed, I
think it'll fail if it doesn't!) I'll be happy to have that happen when
the time is right.
> My primary
> concern is that this not just be a group of people that get together and
> talk about doing stuff but don't actually do anything. And to me, if all we
> do is meet that will not be a sufficiently fruitful result. I want to move
> the ball.
>
> Hank
Agree with you completely here. It's a waste of everyone's time if no
actual change ever comes out of it.
In that interest, then, let's get some action going. You know, an
object in motion tends to remain in motion and all that.
So would you agree with the next step I suggested then? (i.e., get reps
from each of the constituencies to describe the problem from their
perspective.) If so, then why don't we get started on it! I can do a
first draft of the developer issues list. Maybe you (or someone else
here) can start on the entrepreneurs issues list. And perhaps you can
contact some of the people you met at the MIT group to start on their
own lists.
Of course, if you think we should approach this a different way, please
chime in.
DR
Agree with you completely here. It's a waste of everyone's time if no
> My primary
> concern is that this not just be a group of people that get together and
> talk about doing stuff but don't actually do anything. And to me, if all we
> do is meet that will not be a sufficiently fruitful result. I want to move
> the ball.
>
> Hank
actual change ever comes out of it.
In that interest, then, let's get some action going. You know, an
object in motion tends to remain in motion and all that.
So would you agree with the next step I suggested then? (i.e., get reps
from each of the constituencies to describe the problem from their
perspective.) If so, then why don't we get started on it! I can do a
first draft of the developer issues list. Maybe you (or someone else
here) can start on the entrepreneurs issues list. And perhaps you can
contact some of the people you met at the MIT group to start on their
own lists.
Sounds great! Ooh - I'd love to hear who you've got lined up!
Anyway, start I'll drafting up a list of developer issues.
BTW, I'm out of town on vacation next week, so if it'd be possible to
put off meeting till the following week I'd like that, since I'd really
like to be present. But if next week clicks with everyone else for
whatever reason, that's fine too - just someone please take down some
notes on what went down so I can catch up.
DR
BTW, I'm out of town on vacation next week, so if it'd be possible to
put off meeting till the following week I'd like that, since I'd really
like to be present. But if next week clicks with everyone else for
whatever reason, that's fine too - just someone please take down some
notes on what went down so I can catch up.
Write like Yoda, do I? :-)
DR