<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<font face="monospace">also in these respects: <br>
* performance and other optimizations <br>
* use of Python _internals <br>
* Python-specific problems and achievements <br>
interfacing with internet services <br>
* Python if it's used for embedded systems <br>
* Contributions to open source (e.g. OpenStack) <br>
* any clarifications on using recently improved <br>
technologies <br>
<br>
The trick in negotiating with an engineer who <br>
works for a commercial company is to get the ideas <br>
into the engineer's head: what's interesting is an <br>
honest report on Python development and problems. <br>
The contrast might be "we don't want some marketing <br>
person to present us features and an API." <br>
<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 03/18/2016 05:44 PM, jim wrote:<br>
</div>
<blockquote cite="mid:56EC3E67.9010807@well.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<font face="monospace"> I'm okay with talks by developers
working for <br>
commercial Python software in this respect. <br>
<br>
A simple walk through an API is pretty much <br>
worthless. <br>
But commercial development groups do some <br>
eye-opening stuff, and having someone explain <br>
cool stuff is cool, For example: <br>
* techniques and tool chains can be inventive <br>
and helpful <br>
* PyDoc: it's right there and still is badly <br>
underused. If there's a way to get coders or <br>
someone connected with the coding team to <br>
comment properly would be wonderful to know. <br>
Perhaps re-evaluating the nice lady who knows <br>
how to spell (the technical writer) could edit <br>
and therefore enforce proper comments and <br>
develop copy-and-paste type phrases and maybe <br>
paragraphs for common classes and functions. <br>
* Python styles and especially reasons for breaking <br>
the rules. <br>
* Rules of thumb for evaluating licensing. <br>
* A Python-specific use of agile and scrum work. <br>
* QA tricks for detecting circular dependencies <br>
and other subtle miseries. <br>
<br>
<br>
<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 03/17/2016 07:26 PM, K Richard
Pixley wrote:<br>
</div>
<blockquote
cite="mid:b2211734-9f5b-374b-1d42-565b91c19874@noir.com"
type="cite">
<pre wrap="">I'd prefer to stick with open source offerings.
I think of these talks as an opportunity for personal development, not
an opportunity for more advertising. For advertising, someone should be
paying for my time.
If this forum devolves into a purely commercial marketing channel, I'll
be leaving.
--rich
_______________________________________________
Baypiggies mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Baypiggies@python.org">Baypiggies@python.org</a>
To change your subscription options or unsubscribe:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/baypiggies">https://mail.python.org/mailman/listinfo/baypiggies</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Baypiggies mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Baypiggies@python.org">Baypiggies@python.org</a>
To change your subscription options or unsubscribe:
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/baypiggies">https://mail.python.org/mailman/listinfo/baypiggies</a></pre>
</blockquote>
<br>
</body>
</html>