2016-10-03 ~ several things

[theo-armour]

@Abantech/core

Where to post issues

All issues not very directy related to any particular code should be posted to abantech.github.io

Silicon Valley WebGL Meetup

Ricardo Cabello was the speaker. My notes here:

http://www.meetup.com/WebGL-Developers-Meetup/events/234336450/

Aspirations

Nice article. Saying yes is more interesting than saying no.

http://www.businessinsider.com/amazon-unusual-process-to-decide-on-new-products-2016-9

When someone comes up with a possible product idea, Amazon honchos ask themselves, "Can this be fundamentally important to our customers? Can it be game-changing? Can we do it?" he described.

And then they try to think big, he explained:

"We have a thing called 'working backwards.' The first thing we do is we write a press release, ignoring every technical thing we can’t do for now. It’s our aspirations. We also write FAQs where we identify every question we would receive as if we issued the press release. We answer the question in aspirational ways too, ignoring, for the moment, the technical hurdles. In some cases we actually build things."

The idea is to dream about what this product could be.

The next step is to hash out the idea between a team of experts that would potentially work on the new product.

"There's a team in there, in a room, debating, from vice presidents to junior software developers," he says.

Operations repo or folder

We should have a repo or folder where we keep documents relating to designing or specifying the apps we want to build. And we should be talking about how we design our products

[GMelencio]

@theo-armour:

First off - I understand the need to have "several things" as the subject
of this topic. It's because we don't have the appropriate places to put our
ideas and stuff in github. So for now this is OK, but for the rest of the
team's benefit I want to discourage the practice of lumping a whole bunch
of topics into one email. The problem I have is that it's Theo vs James
(yes I'm calling it out now) - who have differing ideas on how to
participate in discussions and team tasking. Theo wants to use github so
that it can grow via community, James wants to use Asana for it's ability
to quickly organize tasks AND because we can use it mobile.Then there's
whatsapp which James uses send direct message or team messages (when Ismael
was with Abantech).

I personally want to use VisualStudio Team Services because it allows us to
have a "wishlist" (i.e. product backlog) that is separate and distinct from
the current tasks PLUS it lets us our commits be associated with specific
tasks so that we know WHY a certain piece of code was changed.

I understand I'm WAY off topic here already, but might as well continue to
finish it....

The problem I have is that if I cater to either one of your preferred
systems the other person stops contributing/communicating - it is getting
increasingly frustrating because of my situation, with my limited time to
try to manage multiple systems. Now I am PLEADING with you both - can you
please suggest/talk amongst yourselves to figure out a happy medium?
PLEASE? Pretty please with sugar - and any and all other vices your desire

• on top? Greg is tired of getting caught in the middle and would rather do
  work than have to manage multiple systems; Coding is not the only thing I'm
  doing, in fact it ends up falling by the wayside because - I have to trying
  to take care of Abantech's image - go to prepare for events, look for
  potential work, which in turn makes me have to post/edit videos create
  charts, diagrams, and send multiple emails to various people every single
  damn day - and on top of that I have to move information from one medium to
  another - serving as the universal conduit between Theo, James, and Greg's
  ideas. HELP ME PLEASE.

Back on topic:

Thanks for good insights shared from the talk. insights from the talk

I was particularly interested in what you said about:

"the insight that marching cubes algorithms - metaballs - can be used to
create and edit 3D meshes. And the the data for these objects can be
humongous. So why not just record the actions that created those objects?
Presto, your gigabytes becomes a few k."

So your saying save the actions to create the objects. This is very
interesting but I'm not sure that your conclusion is correct - not in all
cases anyway. It all depends on HOW it was created. If there was some way
to only pick out the relevant actions then maybe. But here's an example of
what happens with TinkerCAD: I recorded thsi 2 minute video for you:
https://youtu.be/AMTjpo6pDIQ Now, that may not be storage intensive, but it
would certainly be processor intensive and if its processor intensive I
couldn't imagine how it would efficiently work in 3D (espacially VR
applications).

I would like to hear more about the "meatballs" - was this along the same
lines of the question I asked previously (with the plasma currter vs metal
plate metaphor) for mesh manipulation.

On Amazon's approach:

I love it and I'd love for us to implement it. Only thing is that we don't
usually get to meet as a team. Whenever James and I get to sit down and
brainstorm ideas there is SO much we accomplish per minute spent. I wish we
could all get in a room (even virtually) and hash out designs. Sounds like
a good demo too ;)

Operations and folder.

We have a Designs folder in our google drive where we keep a lot of this
stuff. Arguably some things need to be moved in or out of it:
https://drive.google.com/open?id=0B95WMAv7mIgyM3RGc0Nza3A2aWM

The Operations Stuff I feel needs to be kept in a more task oriented system
(like Asana). Apparently a friend of a friend fromt eh University of Sweden
made a github extension that makes it work more like Microsoft Team
Services so that everything is not merely an "Issue" but can be a "Task"
with the additional relevant fields (i.e. what is the "bigger idea"). I'll
look for it but is something to consider, before we go there though, please
see my previous point about all of us using the same system.

Thanks.

Greg

Greg Melencio
CEO and Founder
Abantech LLC
571-402-4688

On Mon, Oct 3, 2016 at 4:43 AM, Theo Armour notifications@github.com
wrote:

@Abantech/core https://github.com/orgs/Abantech/teams/core
Where to post issues

All issues not very directy related to any particular code should be
posted to abantech.github.io
Silicon Valley WebGL Meetup

Ricardo Cabello was the speaker. My notes here:

http://www.meetup.com/WebGL-Developers-Meetup/events/234336450/
Aspirations

Nice article. Saying yes is more interesting than saying no.

http://www.businessinsider.com/amazon-unusual-process-to-
decide-on-new-products-2016-9

When someone comes up with a possible product idea, Amazon honchos ask
themselves, "Can this be fundamentally important to our customers? Can it
be game-changing? Can we do it?" he described.

And then they try to think big, he explained:

"We have a thing called 'working backwards.' The first thing we do is we
write a press release, ignoring every technical thing we can’t do for now.
It’s our aspirations. We also write FAQs where we identify every question
we would receive as if we issued the press release. We answer the question
in aspirational ways too, ignoring, for the moment, the technical hurdles.
In some cases we actually build things."

The idea is to dream about what this product could be.

The next step is to hash out the idea between a team of experts that would
potentially work on the new product.

"There's a team in there, in a room, debating, from vice presidents to
junior software developers," he says.

Operations repo or folder

We should have a repo or folder where we keep documents relating to
designing or specifying the apps we want to build. And we should be talking
about how we design our products

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#8, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEfoMep3UngYXHQk9RRTnJdn9He2451Aks5qwMAYgaJpZM4KMWh3
.