Things I Learned from Delphi CodeRage 8

Mostly from CodeRage 8, but some is from my time working for Embarcadero. I believe I’ve presented at every CodeRage, but this is my first time on the other side. It is also the biggest CodeRage by a significant margin. I’m sure the two events are unrelated, but it is still exciting.

  • Delphi can do functional programming, and it is really cool.
  • Cary Jensen is really excited about FireDAC – and so is everyone else, because FireDAC is really cool. He’s so excited he might cut his hair off . . .
  • There are a lot of really smart and very nice people working for Embarcadero.
  • No matter how easy you find it to understand someone, there is somebody else who has a hard time with their accent, speed, or terminology.
  • There is still more that I don’t know about Delphi then I do. And I think that is a good thing.
  • You really shouldn’t use “with” in your code, especially during a presentation that occurred after Alister Christie‘s session on “anti-patterns.”
  • The Tag property is useful, but no one wants to admit it.
  • Delphi makes it easy to make nice UI and ugly UI. I like that it is flexible.
  • If you use something wrong it will be slow. If you test you can probably find a faster way.
  • Two people can present on the same thing and have different sessions while two other people can present on two different things and have surprising overlaps.
  • REST and JSON are great, but XML and SOAP are still around and in use.
  • If you want to scroll it, use a TListView. Otherwise use a TListBox.
  • When it comes to making custom controls, in any framework, Ray is still the guy.
  • It is a lot more work than I expected to run CodeRage, but also a lot more fun.
  • If you know what you are doing, it is pretty easy to access any iOS or Android API from Delphi.
  • You can use FireMonkey to make a pretty good mobile game, but it still isn’t recommended.
  • Encrypt your customer’s data, or you can get a huge fine.
  • Everyone always likes a good benchmark or comparison, but they don’t really tell you anything.
  • David I. really is as great of a guy as everyone says he is, but even 3 days of CodeRage will wear him out.
  • The Android Emulator is really slow and unresponsive, and no one seems to know why.
  • There usually is more than one way to do something. And just when I think I realized a smart way to do something, someone else will point out an easier way.
  • Replay videos are never online fast enough.
  • Making a good video to explain a technical topic is way more work than anyone realizes, even people who have done it a hundred times. And when you are done you are rarely satisfied with it.
  • GoToWebinar is a pain, but so far it seems to be the best option.
  • Even in a pre-recorded video, people will still help you find the typos in your code.
  • Questions can take longer than the session the questions are about.
  • Delphi developers really are amazing!

And some answers to frequently asked questions:

  • The code will usually be on the presenters blog.
  • Replays will be a couple weeks.
  • Turn on “Use Host GPU” in your Android emulator and don’t run your VM in an Emulator. Better yet, buy an Android device. The emulator is slow for everyone, which is why most Android developers don’t use it.

I learned a lot more, but those were the memorable bits that came to mind.

What did you learn?

17 replies on “Things I Learned from Delphi CodeRage 8”

Replays will be a couple weeks

What is the motivation behind this decision?

#4 full agree. But at least, Pawel has found a workaround by forcing DavidI to learn Polish 😉

Jim, could you setup official CodeRage code repository with a good search capability among the sessions?

The motivation behind the decision is we wanted to get them online as quick as possible. We are attaching the live Q&A since it includes a lot of additional information. Just stay tuned to and the links will start showing up fairly quickly.

A CodeRage repository would be convenient, but probably outside the scope of what I have time to get done.

You say it was the biggest coderage by a large margin. How did it compare to previous BorCons?

Discovered that Android 4.2 and 4.3 report app sizes differently. The 4.2 seems more accurate. Not sure where 4.3 gets the size it reports. Need more research.

Nice overview. It was fun on this side as well. Where did you say those replay videos were? LOL I’m waiting to replay Brian Long’s session about “Accessing the Android API ” . That was quite interesting 🙂

The Android Emulator works fine with HAXM and x86. Besides there are solutions like Genymotion. But you don’t support it and new devices are built on Intel.

@Artur: I’m not seeing many Atom based Android devices in the US, but they are starting to show up in other countries in limited numbers. Currently everything I see shows ARMv7 holding a very dominate lead. If Atom (or MIPS) starts to gain traction then maybe we will see support for it.

@John Jacobson: A lot of the BorCons were Developer and Database tools conferences combined. This was bigger than the Developer only BorCons and similar to the combined BorCons.

Comments are closed.