Archive for the 'thoughts' Category
This is a continuation post from Google I/O Day 1.
With a fresh perspective after the Day 1 sessions, I reworked my schedule to try and make the most of what Google I/O had to offer. The keynote for Day 2 was given by Marissa Mayer, which admittedly made me a little star struck. I read about her in The Google Story- she was the first female employee and part of the first handful hired at Google. I thought it was pretty cool that she was addressing us. Of the advice she had to offer, she mentioned something also mentioned in The Google Story; have a healthy disrespect for the impossible. It was this thought that constantly lead Larry, Sergey, and the rest of Google to do the things they do. It’s what made Larry and Sergey start Google. So with that phrase in mind, I went on to Day 2 of the conference.
I did two things I didn’t get to do on Day 1: A Code Lab and a Fireside Chat. For the code lab, I worked with the Google Maps API. The lab was incredibly helpful. There was a website with about 24 slides showing different things you can do with the API, some of them being demonstrated by the Google developer running the lab. Then we were given a link to instructions and got to work at our own pace making different API calls. Developers, of course, were there to answer any questions we had.
Then there was the Fireside Chat I attended, which was on the topic of Android. Eight engineers from the Android team were there to informally answer questions as long as we could come up with them. I didn’t ask any, but plenty I had [or should have had] got answered.
All in all, this was a pretty great learning experience that gave me a lot of new insight not only on Android, GAE, or other Google products, but Software Development in general. Just hearing some of the engineers speak was truly inspiring. It was also eye opening to the fact that there is so much I need to learn (not that I didn’t know that already, but this made it a little more concrete). And not only did I learn about software development, but also about running a business, how to treat users, and some new ways of thinking and problem solving. I feel they took the “Cura Personalis” approach the University of Scranton takes (translates to ‘Care for the whole person’). The people at Google know what it takes to teach and to get people to learn.
So will I do it again next year? You better believe it.
May 30th, 2008 | 
No Comments » | 
Google, IO2008, Software, computer stuff, thoughts
When I first got to Google I/O I made note of a few things. “It’s like 85% male,” “Wow there are a lot of smart phones,” and “There are a lot more Macs here than I thought there would be.” Of course, once I was all checked in, settled and the keynote started, I was nothing less than blown away by what they had to show us. I can’t really recap everything covered, however I was really struck by the Google Web Toolkit. The GWT allows you to write programs in Java and then convert them to AJAX (Javascript, etc.). To be honest, I didn’t even think that was possible. The app they demonstrated was incredibly powerful, seamless and fairly quick. You’d never think it was a web app. And that was just the tip of the iceberg. Google I/O Day 1 showed me the raw and very real innovation going on at Google.
Aside from GWT they wowed us with a working Android prototype, which you can check out here. What really got me was the compass mode, which gives you a live street view that moves based on what compass direction you’re facing. The android talks I attended gave us a quick intro to and the basics of creating an android app. Those talks helped me get my own environment up and running, which I was able to do in no time flat. While I didn’t look that much into it today, I also gained an appreciation for Google Apps Engine and am going to learn Python so I can develop on it. But it wasn’t all work at Google I/O today.
Aside from the numerous breakout sessions and coding labs, Google offered it’s attendees colorful beanbag chairs, pool tables, a candy bar, and fully stocked cooler. From 6-10pm there was also “Google After Hours,” which was a mixer with a DJ and live band, food, open bar, a few Wii consoles with the games projected on giant TVs, and arcade games and pool tables scattered all around the room. In short, Google can throw a party.
What I got out of today’s session was learn Python, and get better at Java. On tomorrow’s agenda is GWT, more Android, and AJAX design patterns. As nerdy as it sounds, I’m pretty excited. I’ll be posting pics and a follow up to this post tomorrow night.
May 29th, 2008 | No Comments » | Google, Java, Javascript, Software, computer stuff, thoughts
I officially finished with the semester on Monday, got home from school yesterday, and am finishing up Bringing Down the House; so I think it’s about time to build my 2008 Summer Reading List. A few weeks ago I came across the Essential Man’s Library, which is where I’ll be pulling most of my choices from.
- Heart of Darkness by Joseph Conrad
- I read the abridged version as an undergrad for a class, so I didn’t really read it.
- The Idiot by Fyodor Dostoevsky
- Heard of it but never read it. Sounds a lot like me though.
- Faucault’s Pendulum by Umberto Eco
- I’ve never actually heard of this one, but it sounds like a really good read.
- The Are of Warfare by Sun Tzu
- I started reading this one a couple of years ago but never finished.
If I have time, I’d also like to revisit The Great Gatsby, which I’ve been meaning to do for a while. I liked it in high school but I feel like I didn’t understand as well as I would now.
May 24th, 2008 | | books, thoughts
Wow. I just realized I haven’t posted here since the end of April. And really, I have some ideas for posts, but no time. I am in the midst of finals week, projects, and getting ready to go out to San Francisco for Google I/O. I also have some ideas for projects I want to do over the summer. So in light of that, here is a “Random Thoughts” post to hold you over until I have time to write something more substantial.
- I finished A Confederacy of Dunces. It was very good. I am now reading Bringing Down the House, the book the movie 21 is based on.
- Iron Man was an awesome movie. Go see it. Take me with you.
- I am using a new system to keep track of invoices and expenses for my business. That will be my next big post.
- Google Reader integrated Notes and the ability to share websites not in your feed reader, as I requested in my last post. It’s like they are listening directly to me!
I frequently have random thoughts that I will post on Twitter, if you’d like to follow me.
May 13th, 2008 | No Comments » | thoughts
Over at LifeHacker, they are hosting a spirited discussion on what the programming language to learn first is. I think this is a pretty interesting discussion to have and want to comment on what the others are saying, as well as justify my stance. First of all, I did weigh in, saying:
I’d say if you’re not going to be a serious applications programmer, learn some weak-typed language like PHP or Javascript first to get your feet wet with program logic without having to worry about whether your types (the difference between say a number and a word) are correct. This will help you with the control structures(if statements, loops), how the logic works and how to solve some basic problems. Then you can move on to a more advanced language and learn the different types, objects, etc.
Many of the others who commented said that Javascript is not a programming language, it’s a scripting language. Is there a huge difference? Maybe, but not to someone first learning. They will not be doing things a programming language calls for- they will be learning control structures and how a program works, what kind of logic goes into writing a program, etc. To be honest, I first learned Java when I was a freshman in college, but I didn’t really understand programming until I picked up PHP over winter break of that academic year. So is there a difference? Sure. Is it a huge deal to someone starting out? Not at all.
Then we’ve got those who say, “Learn C first, it’s the best” or someone even said, “Learn Assembly.” I know how to program and Assembly is hard. You’re not writing code in something that looks remotely like English and you need an understand of how data is represented on a machine. It sort-of applies for C too, as C is a low level language. Don’t get me wrong, C is the best language I’ve coded in- it’s fast and you can do really powerful stuff. But I think pointers alone is enough to turn someone off to C and programming in general.
Finally, we’ve got those who say learning an Object Oriented (OO) language is the way to go. I can see that. I feel there is enough abstraction there that the learner might be ok. They shouldn’t dive right into object, however, because objects are pretty difficult to visualize if you’re just starting out.
I still say my approach is at least a good one. Learning a simpler language that doesn’t put restrictions on data types will allow the learner to focus on program logic more than data representation. They will begin how to think like a programmer and can move up from there. PHP isn’t a bad place to start because it acts like a simple language (weak typed, syntax is pretty easy to understand), but you can do some powerful things like create objects.
Teaching yourself to program is a pretty daunting task to begin with. However, if you pick up a good book and start with a simple language, you should be fine.
PS- HTML is not a programming language. It’s a Markup Language. You will not learn anything about programming.
April 4th, 2008 | No Comments » | C, Code, thoughts
Email correspondence is my normal and most practiced form of communication because of the convenience for both parties. It allows you to quickly send a message to someone and know (in most cases) they will get it the next time they check their inbox. I feel it’s also better than instant messaging or phone conversations in some instances because it allows me to think about what I want to say. However, with the amount of emailing I do, I notice many people don’t know how to write what I deem a proper email.
Since I am a TA, I get a lot of emails from students like this:
Hey do u take off for late assignments
This is sometimes forgivable as it’s mostly freshmen who are relatively new to email as the defacto form of communication. I am sure when I was a freshman my emails weren’t up to my own current standards. However, even dealing with clients I get some of those emails that come off as less than professional. Using SMS shorthand or incorrect punctuation, spelling errors, etc. are some of the problems I run into. Here is an example of what I would say is a proper email:
Joe,
I hope all is well. I was wondering if you took off for late assignments.
Thanks,
Jim Student
The later email includes some important details the sooner email lacked. Here are some ground rules for a good email:
- Address/Greet the person you are writing. It looks better and it ensure you know who are you contacting. The greeting might not be necessary, but it shows you care at least a little.
- Use proper grammar. This isn’t instant messenger and your emails will be read more carefully. You don’t want to be judged on simple grammatical errors. Also, use real words- not shorthand. “U” instead of “you” might be ok for texting or IMing, but it’s not for email.
- Spell check! I’ve been guilty of this from time to time, but now that most browsers have spell check built in, there is really no excuse. This goes along the same lines as grammar checking- and this is much easier to avoid.
- Sign your name. Let the person you are contacting know who is emailing him. Usually for the first email I will also include my last name, and then drop it in any replies. This one drives me crazy because, especially with my students, I deal with a lot of people and don’t always recognize the email address.
-
These four simple checks will make for an infinitely better, more professional looking email which in turn reflects better on you. Did I leave anything out? Disagree with me? Let me know in the comments.
March 26th, 2008 | | Life, computer stuff, thoughts
