Since moving to Las Vegas, I’ve joined the PHP Users Group. Overall it’s been a great experience meeting people in the community and hearing about more PHP stuff. Since I’ve been there I’ve given a few talks and figured I should list them here.
First up, a talk that was an introduction to CakePHP. Probably my best talk out of the three listed. It was informative, with lots of questions and I knew the material really well (one would hope considering it is my day job).
Next was a talk on Ember.js, this one didn’t turn out so well. I under prepared for it, and it showed. It also didn’t help that I mostly based my talk on a co-worker’s slides. Overall this was novice hour for me. Moral of the story — don’t give talks unless you know the information and don’t try to base a talk using someone else’s work.
Last presentation was one on PHPUnit, which went ok. I knew the material better than the Ember stuff but there were a few weak areas. Overall I think it went pretty well but it could have gone better.
Some random thoughts on public speaking
Public speaking (of a sort) is something that I used to do much more often, it’s been good to stretch that part of my brain over the past few months and get a handle on delivering talks that deal with technical information for a generally technical audience. It is definitely something I want to do more of in the future and to get better at.
Not everyone may want to do this type of thing, but if you are interested in it, I would urge you to give it a shot. It is easier than what you think. I would suggest pick a topic you are very familiar with and can answer questions on the fly about. Feel free if you get a question that you can’t answer to say so, rather than present imprecise information.
I’m just explaining what I think about when I’m making decisions regarding performance and scalability. If I assumed that there would never be a way to automate adding notes, I might be correct — but I’d be guilty of malpractice. The engineering department doesn’t have the luxury of making that assumption.
I enjoy this bit “engineering department doesn’t have the luxury of making that assumption”. As a consultant it’s even truer that I can not make assumptions especially since I don’t have any special insight into the business. As an engineer we don’t have a luxury of making assumptions in general but especially when it comes to the amount of data that an end user might stick into our software, we have to offer support for all our users in general.
lolcommits takes a snapshot with your webcam every time you git commit code, and archives a lolcat style image with it. Git blame has never been so much fun.
Find out just how coherent you were for that 3am commit.
When you begin entering your card number, Skeuocard attempts to match it to an accepted card type. Once it is able to do so, it modifies the layout of the card to match the card product (Visa, MasterCard, etc) and makes any tweaks specific to the issuer — for example, the special layout of the Chase Sapphire card.
As you enter your information, Skeuocard modifies the underlying form values from your original, non-enhanced form. It also validates each field to find simple user mistakes and missing fields.
If the card product has fields on both sides of the card (for example, placing the CVC code on the back) the user will be prompted to flip the card to fill in the remaining fields.
Pretty cool use of skeuomorphism, makes it really easy for someone to validate that the credit they entered is their credit card. Even better it’s on Github, so feel free to make it better.
Like many of my fellow developers, I am in the middle of an update of an app for iOS 7. As you’d expect, it’s a lot more work than previous versions of iOS. But results are stunning: both David Lanham and I have commented that our shipping version was “feeling old and clunky.”
While cranking along on the update, a couple of thoughts occurred to me: how many other developers were doing the same thing and were they going to commit fully to iOS 7? The depth and breadth of the changes in iOS 7 makes it difficult to support older versions of the OS.
So I just asked. I also included a simple question that any developer who was actively working on an update would be able to answer as a sort of CAPTCHA.
After a little over 24 hours, I had my answers:
The percentage of developers supporting iOS 6 and 7 is higher than I would have thought.
The inventor of the Web, Tim Berners-Lee, had never testified in court before last year. In February 2012, he left Cambridge to fly down to Tyler, an east Texas city of about 100,000, to testify at a patent trial. It was the culmination of a bold campaign by a man named Michael Doyle to levy a vast patent tax on the modern web.
Berners-Lee was one of several web pioneers who came through the court during the course of a four-day trial, which ultimately convinced a jury to invalidate two patents owned by Eolas, the tiny patent-holding company that Doyle and his lawyers transformed into one of the most fearsome “patent trolls” of all time.
Now Eolas appears to be gone for good. The company mounted a lengthy appeal, but it was all for naught; this morning, a three-judge appeals panel affirmed the jury’s verdict without comment.
This was a particularly bad patent troll for the web.
Tagged with: business
, patent troll
Posted in Computer Science
Short Link: http://jty.me/1bYC1r2