Codetown ::: a software developer's community
A good time was had by all at last night's GatorJUG meeting. Kevin Neelands discussed Android Design Patterns in the context of his recent work on the job with an Android app. The lessons learned he presented were not just interesting but huge timesavers for him. They also dramatically increased app performance. Here's a photo of Kevin:
We had a couple of folks who work at local shop Infinite Energy attend. Here Curtis McMillen describes the Observer pattern:
Hopefully, Curtis will give a presentation soon on some features he's particularly impressed with that are now part of the Java 7 distro. Stay tuned.
A good time was had by all. Thanks, Kevin!
Tags:
After Curtis talked about the new features in Java 7 I went home, got on Amazon and ordered a book on it. Sounds like exciting stuff!
Well, I ordered a Java 7 advanced featues cookbook but it turned out that was not really what I wanted. So I just got on amazon and searched specifically for java annotations and found 2 books the reference dependency injection in their description. I enjoyed giving the talk, even tho the audience knew the topic I felt I got a couple new things across, the questions afterwards helped me explain the parts I kinda glossed over, and Curtis building on it by explaining the latest java has intrinsic support for the observer design pattern was a learnin experience for us all.
I wouldn't say I "knew" the topic, maybe I was very familiar with it. :) But even still, there's always something to learn. For me, it was inner classes. I know what inner classes are and I've even used them a number of times without ever stopping to ask why? What are they good for and when is it appropriate/inappropriate to use them? What effects do they have on memory vs non-inner classes? I ended up going home and digging deeper on inner classes and I actually found some pretty interesting things that I'll be blogging about pretty soon. So thanks!!
Kevin Neelands said:
Well, I ordered a Java 7 advanced featues cookbook but it turned out that was not really what I wanted. So I just got on amazon and searched specifically for java annotations and found 2 books the reference dependency injection in their description. I enjoyed giving the talk, even tho the audience knew the topic I felt I got a couple new things across, the questions afterwards helped me explain the parts I kinda glossed over, and Curtis building on it by explaining the latest java has intrinsic support for the observer design pattern was a learnin experience for us all.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.
Join John O'Hara, creator of the Advanced Message Queuing Protocol (AMQP), as he shares the compelling journey of this groundbreaking technology at QCon London. Discover the intricate dynamics of collaboration, challenges faced, and the human element in open standards. O'Hara's insights illuminate the politics behind technology development, proving vision is as vital as innovation.
By Steef-Jan WiggersPlanetScale has recently announced that vector support is now generally available. Created as a fork of MySQL, this new feature allows storing vector data alongside an application's relational MySQL data, removing the need for a separate specialized vector database.
By Renato LosioShawna Martell shares practical strategies to effectively manage legacy code and tech debt. Learn how to lift existing code, gain buy-in for improvements, and build new systems with future maintainability in mind using encapsulation, testing, and linting. She explains the Strangler Fig pattern and provides actionable advice for creating code that ages gracefully and minimizes future headaches.
By Shawna MartellA rigid hierarchical dynamic between senior and junior software engineers can stifle innovation, discourage fresh perspectives, and create barriers to collaboration. According to Beth Anderson, senior engineers can actively learn from their junior counterparts. She suggests creating an environment of mutual growth, psychological safety, and continuous learning.
By Ben LindersFor systems that require strict synchronization—like distributed databases, telemetry pipelines, or event-driven architectures—handling leap seconds incorrectly can lead to data loss, duplication, or inconsistencies. As such, managing leap seconds accurately ensures system reliability and consistency across environments that depend on high-precision time.
By Craig Risi
© 2025 Created by Michael Levin.
Powered by