24. November, 2011
Some pros and cons:
There are two minor points: The console is pretty big and the in-page version can’t be moved.
Blackbird is a really small logging framework. No frills, just the basics. So no exception logging, for example. A profiling option is the most complex feature. In the world of the logging frameworks, it’s the iPhone: Nice look and only the useful features. The console is always in page, it sits in one of the four browser corners, it can be hidden and shown with F2.
My main complaint about Blackbird is that you can’t use the mouse to move the console. Also disabling the framework needs several lines of code. A single variable would have been more comfortable.
23. November, 2011
There are various attempts to get Java and SQL to behave with each other. We have JDBC, OR mappers like Hibernate and EclipseLink, language support like in Groovy. All of those have advantages and drawbacks.
JDBC is powerful but low-level. The API is not really friendly. You need to write a lot of boiler plate code for even simple tasks.
Languages like Groovy wrap JDBC to make simple tasks simple. The code becomes much more readable but changes in the database schema become runtime errors.
OR mappers try to turn a relational database into a OO database. It works better than you’d expect but it also causes odd problems and leaks into design of your code: You must no’t use the ID field in equals, hiding the session in a thread-local variable can cause exceptions when you use lazy loading, failing to understand the requirements of the OR mapper causes spurious bugs. At least the OR mappers will complain when the schema changes.
Enter jOOQ. It’s like a OO wrapper for JDBC:
- You get all the power of JDBC if you need it
- The readability of a fluent interface
- The database schema is part of the code (so you get compile time errors if it changes)
- You can iterate over results as if they were a plain Java collection
8. November, 2011
If you’re with a big company and want to do it “right”, chances are that you’re only allowed to deploy during the night, on weekends and never, never, never in December (or any other date were mission critical systems must not fail).
Looking for some reasons why this is wrong? Go here: Why are you still deploying overnight?
In a nutshell: You’re deploying overnight because your processes are brittle, the product is riddled with bugs and you have no fall-back strategy.
Overnight deployment is nothing but a red flag saying that you’re not doing it “right”.
2. November, 2011
If you need a framework for vector graphics, try Raphaël.
MIT License, impressive demos, readable source code.