Many time, in the middle of developing a user story, the programmer discovers a question about how it’s intended to work. Or the tester, when looking at the functionality that’s been developed, questions if it’s really supposed to work that way.
The author recently made the decision to migrate from MySQL to PostgreSQL (the reasons why to be covered later). He thought he'd just jot down my notes on a tool he tried to help with the migration: SQL Workbench/J Data Pumper (no sniggering at the back).
There are a tremendous amount of SQL APIs natively written in Scala. One API that we want to focus on in particular is ScalikeJDBC (licensed ASL 2.0), which has recently published a SQL query DSL API similar to that of jOOQ.
Patterns & Practices are key indicators of any application development life-cycle, whether it’s Windows Store/Desktop app, Web, Cloud, mobility, or LOB app. Microsoft P&P leverages few new patterns as well for Cloud based apps. Lets have a summation as followed.
The author has been hunting for good database tools to perform that class of tasks that we all need, but that we end up re-implementing over and over again. One such task is database migrations. He's been experimenting with Goose to provide general-purpose database migration support.
One of the riskiest parts of a deployment is updating the database schema. We’ve argued for years that you should automate these processes. The most common first step in that direction is to take the SQL scripts you’ve been using and treat them as incremental versions in IBM UrbanCode Deploy.
Moving toward Continuous Delivery can be a big change. Ideally, releases speed up and smaller, iterative changes allow for quick fixes and less risk. But any team undergoing changes will experience growing pains. Let us know with a comment: What has your experience with Continuous Delivery been like?
Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Troy Hunt, Software Architect and Microsoft MVP for Developer Security.
As someone who has been around programmers (and ran a Java Users Group) for about 15 years, I often guide senior technologists in marketing their skills. I generally advise my clients on employing some senior level engineers who are strong coders but will also serve a secondary purpose of attracting other less experienced hires.
If we’re doing things correctly, almost everything we write should make the next release or next project easier. Effective reuse taps into the passion developers feel for great code, leading to greater creativity and productivity. Besides, how many Foobulators does one company need, anyway?