Showing posts with label OSS. Show all posts
Showing posts with label OSS. Show all posts

Monday, July 15, 2013

DFW Pythoneers 2nd Saturday Teaching Meeting, July 13, 2013

18 Pythoneers showed up at the The Collide Center in McKinney. John Zurawski and Joesph Weaver found the location, and John was the gracious host and leader for the meeting. The venue was great, but unfortunately for us the meeting space will become more space for startups afterwards.

Upcoming Events

Kevin Horn announced that PyTexas 2013 is August 16-18 in College Station. Early registration ends July 16th.Friday is oriented towards tutorials and training. See the web site for details.

July 18th is Project Night at Gazeebo Burgers in Frisco from 6:30 to 8:30. There's a separate meeting room that I'll request and the WiFi is usually good. Topic is pandas and data analysis, so show up prepped with software loaded and data to rip. If you are having difficulty loading all the required packages, consider loading the Anaconda distribution from Continuum Analytics.

July 20th is Moon Day at Frontiers Of Flight Museum at Love Field in Dallas. Our buddies at DRPG will be demoing various robots, plus there will be other cool displays. Moon Day is my favorite unofficial holiday, so even if you can't attend, pause for a moment and realize what an awesome achievement the Apollo program was...

July 25 will be the normal casual meeting at Taco Cabana in Addison. This is a informal get together to chat and network with other Pythoneers and techies. If you are seeking a solution for a problem, ask around and chances are someone can help you. Otherwise, just geek out and enjoy the company.

Group Discussions

One of the main topics of discussion revolved around meeting locations and meeting content.

Meeting Space

In the past the group has had corporate sponsors whom had meeting facilities. Currently we need locations for Saturday teaching meetings and alternative sites for the 4th Thursday informal meetings. I can lead the 3rd Thursday Project nights at Gazeebo Burgers.

An ideal teaching location would be central, easy to find, with a room for 30 or 40 people, WiFi, power outlets and restrooms. We also need a slightly large venue than Taco Cabana for the casual meeting since the largest table there is about eight seats.

Meeting Topics

There was an active discussion about Topics, Teaching, Presentation and Projects/Challenges. John proposed a meeting structure that works to start the meeting. and the group discussed various ideas for the "meat" of the meeting. It was recognized that people into Python have different needs, skill levels and interests. Some of the various topics brought forth:

Web Frameworks 
  - Flask
  - Django
  - Idea: Framework Shootout - Simple web app spec; write it in diff frameworks
    Related: find a way to allow beginners to work on subject area before talk

- Database?
  - ORM's

- REST API's in Python

- Network Programming
  - Twisted / Tornado

- Scientific Computing
  - Pandas

- Game Programming

- IPython
  - IPython Notebook

- Python eco-system/community

- Best Practices
  - PEP8
 

Sharknado

 The breakout presentation of the meeting  was John Zurawski's pixel accurate clone of Sharknado done in cocos2d. Most awesome use of Python, ever!

Challenges

It was observed that  programmers don't learn unless they have projects or challenges. So I'm borrowing a Python challenge from elsewhere and will be working on this particular project in my spare time in the next couple of months. Let's swap notes and review code at a meeting in the future if you are interested. :)



Monday, July 1, 2013

DFW Pythoneers Meeting June 27, 2013

13 Python enthusiasts showed up at the Taco Cabana in Addison for the monthly meeting. There was some confusion about the meeting location and some participants were disappointed with the lack of formality. Overall most of the attendees enjoyed themselves and there was much discussion about Python and related topics. This was the largest group that has met up for the Thursday night meetings.

The good news: We may have found a space for the upcoming 2nd Saturday Teaching Meeting. Joseph Weaver mentioned that John Zurawski had found a possible meeting space in McKinney. John got in contact with me and will try to contact some of the more veteran members and leaders of the group. From what I've heard of the location, it will be good for the larger teaching meetings.

The challenge: With increasing attendees, Taco Cabana is difficult to have more than the most casual of meetings. I spoke with Jay, who said that this meeting has usually never been larger than 4 to 6 participants. If you wish to have a larger space that is more conducive to larger meetings, we're open for suggestions. Key things to consider are central location since we attract folks from 20 to 40 miles away.

Tuesday, March 12, 2013

Netflix and Python

There's a nice post on their technical blog about how Netflix uses Python.

I found this section quite interesting:

Data Science and Engineering

Our Data Science and Engineering teams rely heavily on Python to help surface insights from the vast quantities of data produced by the organization. Python is used in tools for monitoring data quality, managing data movement and syncing, expressing business logic inside our ETL workflows, and running various web applications to visualize data.

One such application is Sting, a lightweight RESTful web service that slices, dices, and produces visualizations of large in-memory datasets. Our data science teams use Sting to analyze and iterate against the results of Hive queries on our big data platform. While a Hive query may take hours to complete, once the initial dataset is loaded in Sting, additional iterations using OLAP style operations enjoy sub-second response times. Datasets can be set to periodically refresh, so results are kept fresh and up to date. Sting is written entirely in Python, making heavy use of libraries such as pandas and numpy to perform fast filtering and aggregation operations.


Here's the video from PyCon 2013: http://pyvideo.org/video/1743/python-at-netflix

Monday, February 25, 2013

Pragmatism vs Partisanship


You ate Chinese food, so obviously you must hate Europeans...

Sounds silly doesn't it? So was the type of reaction I got from a data professional when I showed him a new book on data analysis that I was excited to add to my library. The software language didn't match his worldview or career investment, so I was labeled a "Microsoft basher".  Which is silly since we were at event for users of Microsoft software, I was using a Windows phone and two out of the three operating system I was running on my laptop were Windows 7 and Windows Server 2012.  And I spent much of the time taking notes in OneNote and discussing PowerShell 3 and SQL Server 12 with my cohort.

And the irony of situation is that Microsoft and many of it's employees and advocates recognized that not all the great tools and goodness flows from the mother-ship in Redmond. Buck Woody, a author and well known Microsoft database and Azure evangelist recommends installing OSS text-handling utilities when setting up your Data Science Laboratory. Another well known Microsoft technologist, Scott Hanselman, suggests many third party tools and has a recent post discussing GitHub and line endings. With the existence of CodePlex,the inclusion of Git support  in Visual Studio and offering Linux VMs on Azure, Microsoft is becoming more pragmatic and inclusive in regards to OSS.

And OSS has growing garnering commercial support. Red Hat has been making money for years. VMware supports both commercial and OSS hosts and guest. Some of the projects on CodePlex get adopted by commercial companies. And data analysis tools featured in the book that seed of this post have commercial support from a company, Continuum Analytics, which just received a grant from DARPA, to further develop their tools.

So, while disappointed in the reaction I received from this individual, I still respect him and hope to demonstrate the power of using both OSS and Microsoft tools together to tackle some tough data problems.