- Signups are open for Delphi Developer Days. Remember, the “Very Early Bird” special price ends on August 12, so start planning now. I love presenting and hanging out with Delphi developers, so I hope you’ll be at one of the events. Should be a very fun time all around. And of course, if your company wants to help sponsor the event, then please be sure to contact Cary via the website.
- RAD Server is the latest “official” product at Embarcadero. (It previously was known as the Enterprise Management Server and was a feature of high end Delphi SKU’s). This is a cool tool. It’s basically an “AppServer” to Delphi as AppServers are to Java Enterprise Beans (or at least as I understand it). It in effect makes it pathetically easy to build REST APIs. Microservices are all the rage, and so this is a well-timed release. I’m definitely going to investigate it.
- Book Update: You can find out the basics of my new book here. You can also sign up to get email updates, and help me price it by letting me know what you’d be willing to pay. Currently the book is being proof-read and is under technical review. I can’t say for sure when it will be available, but it’s definitely in the “The last 10% takes 90% of the time” stage. I just realized that I hadn’t covered attributes enough, so I’m going to have to add a section on that.
- I simply cannot say enough good things about CodeInsightPlus. Here’s the one thing I will say. If you value your time even slightly, get it and install it now.
- This blog post by Marco started an interesting discussion. For what it’s worth, I stand on the side of proper encapsulation, after having originally been on the other side of the argument.
- In my post about my new book, I mentioned that I thought my outline was a little thin, and indeed it was. I left out a large topic about which I planned on writing – “Writing SOLID Code”. Add that in, and things seem a bit more fleshed out. The silly thing was that I was working on that chapter when I put together the outline and wrote the blog post. Anyway, the outline has been updated and all is well. Thanks again for the support. If you want to keep up with the book’s progress, help out answering my silly questions, and generally be supportive, you can sign up at the LeanPub site, or you can join the Google Group.
- Here’s some food for thought for my post about not using nil – The Null Object Pattern. Yet another reason never to return nil. Instead of doing that, you can return a null object that won’t cause an access violation and yet won’t do anything. You can check if the object is a null object if you need to. Win all around.
- So the rumors were true – Embarcadero has bought the main products of TwoDesk Software. Jacob Thurman has stated that while he’s not now an Embarcadero employee, he will be working on the Delphi IDE. I guess it’s none of our business exactly what the relationship will be, but if Jacob is working to improve what the IDE can do with code and to improve developer productivity in the Code Editor, I’m very happy. I know that Jacob has had a lot of things that he wanted to do, but found it difficult as an “outsider”. Now that he’s an “insider”, I hope he can do them. I think we’ll see some fun stuff coming out of this deal. Congratulations to Jacob, who I hope was well remunerated, and to Embarcadero for the wisdom to see and acquire Jacob’s skills.
- True words tweeted by me: “There are two things that developers love to do: Make pronouncements, and point out the exceptions to other developers’ pronouncements.” I like to make pronouncements as you’ve probably noted. I’m always trying to learn new things and new ways of doing things, and I don’t want to be held back by the “well, we’ve always done it that way” way of thinking. I believe that the way software is developed is evolving and improving, and that we’ve found new ways of doing things better. I try to learn those things and blog about them. That’s what I’m trying to do here. If you disagree with what I say, I welcome your comments. But I ask you to consider that maybe I’m actually on to something. I’d encourage you to take the same path I have – the path of learning these new things that developers are finding and doing. For instance, I don’t ever intend on writing another Delphi application without utilizing MVVM. But ten years ago, such a thought would have occurred to almost no Delphi developer. I encourage you to study the SOLID principles, to read Clean Code, to find better ways to decouple your code, and to generally seek out new thinking about software development. I’m a firm believer that there is always a better way, and I encourage you to think so as well.
First of all, I want to once again thank all of you who have purchased, read, or otherwise supported my book Coding in Delphi. I’ve said it before and I’ll say it again — the response has been overwhelming and humbling. The book has been more successful than I could have ever hoped for.
It’s so successful, in fact, that I’ve decided to write another one – More Coding in Delphi. I am once again using the LeanPub publishing platform. LeanPub is really an interesting tool – it makes it really, really easy to produce a book. Highly recommended. You write the book in Markdown, and they take that and turn it into PDF, MOBI, and ePUB files for you. Easy as pie. I’ve been using MarkdownPad for writing the book. It does a nice job of helping you write Markdown text.
By default, LeanPub uses DropBox. First, I granted LeanPub access to a shared folder on Dropbox. Then, when I go to publish a preview or the real thing, LeanPub looks in that folder for a file called “Book.txt” which describes the format of the book by pointing to *.md files. It then accesses those files in the shared folder and creates the book.
This time around, though, they’ve added a new feature where you store the book in GitHub and they pull from the repository to get the files for the book. Cool. When the book is ready for proofing by any of you interested in doing so, you’ll get access to the manuscript by pulling it from the private repository on Github. So if you want to help out, you’ll need to brush up on your Git. It also means that I get the benefits of a DVCS, and you guys can make pull requests if you have improvements for me.
Right now, the outline for More Coding in Delphi is currently:
- Four Thoughts on Coding Before We Start
- Encapsulation, CQS, Postrel’s Law, Compostion over Inheritance
- Duck Typing
- Aspect-oriented Programming
- Design Patterns
- Observer Pattern
- Adapter Pattern
- Decorator Pattern
- Another Pattern to be named later
- Another Pattern to be named later
- Parallel Programming
That feels a little thin to me right now, so I am seeking more topics. If you want to suggest anything, I’m all ears — either comment here on this post, or join the Google Community for the book. Remember the philosophy of the book, though – it’s all about the code. I’ll write about code frameworks, RTL type stuff, etc., but I don’t want too many screen shots of forms in the book. There will be some in the MVVM chapter, but the idea is that the book covers code and how to write good code. That’s what I want to focus on. I’m also open to turning “Four Things” into five or six or seven things, so if you have small topics – a page or two, not enough for a full chapter — I’d love to hear those as well.
Okay, so now the real work begins. It’s a lot of work to write a book. My hope is to have the book published by the end of this year. I know that I can’t do it without your help – you guys made the first book possible. Again, I’m grateful to all you readers and supporters.