Many of the projects I’m involved in use Maven as build system due to its reliability, widespread use, and flexibility. However, I often find myself hurdling around bad choices with regard to the build process. In this article I’d like to illustrate some of the most useful techniques to implement flexible, adaptable, and secure builds with Maven. Download the example project from GitHub Key requirements of an enterprise build Enterprise projects have demanding requirements when it comes to configuration and build management.
Modern web applications using React and other frameworks are often distributed as static websites. It is undoubtely the simplest, cache-friendly and dead-cheap solution. However, some enterprisey projects (think about data-entry and legacy-business applications) need to be deployed in a standard, more constrained environment like a Java JEE Servlet engine, if not an actual application server. Forget having your app deployed on a separate web server (like Apache or Nginx), let alone a dedicated 3rd-level domain or IP address like frontend.
I have to admit: I really enjoy creating websites, but I’m awfully lazy when I have to work on my own! Over the years I’ve tried different languages and tools. In the early days I used to manually edit all the HTML pages by hand, which I regretted immediately. So I started writing my own shell scripts, Java programs, XML formats and whatever. My first open source project ever was devoted to this: Web site Generator.
Software development is hard. Organizations, small and large, can be very inefficient sometimes: people waste their energy on endless meetings, vague specification documents, pointless “reply-to-all” emails. Working as a freelancer in such environments is perhaps even worse, as you’re supposed to be the hyper-efficient 10x developer unicorn that can make any problem magically disappear. In this article we will see how, with a couple of simple tools, we can reduce noise, improve efficiency and guarantee better accountability.
Update 2017-08-01 Updated “Behavior-Driven Development (BDD) and Test-Driven Development (TDD)” section, adding bddblock template I’m a IntelliJ IDEA user since late 2013. After a long (and not without problems) liaison with Eclipse IDE, and before that with the glorious Borland JBuilder, I wanted to try something new. Not that Eclipse was bad per se, it was just getting heavier and buggier release after release, and the plugin ecosystem wasn’t anymore something you could rely on.
È ormai da un po’ di tempo che ho imparato a giocherellare con Groovy e devo dire che lo sto apprezzando ogni giorno di più. In questo articolo voglio mostrarvi come sia facile simulare, utilizzando Groovy e la libreria Apache Commons Math, i dati di carico tipici di un server che lavora 24/7, con tanto di picchi di lavoro durante le ore diurne. Due parole su Groovy A suo tempo mi misi a cercare un nuovo linguaggio di programmazione oltre a Java (non vi preoccupate, continuerò ad utilizzarlo per molto tempo ancora!
It’s been a long time since I wanted to read this book, given enthusiastic reviews from various influential programmers. After “digesting” it (it took me almost three months) I can confirm the absolute value of this publication! Title: The Pragmatic Programmer: From Journeyman to Master Authors: Andrew Hunt, David Thomas Language: English Editor: Addison Wesley Book Structure The book has a very free-form structure, the single chapters are not meant (except a few exceptions) to be read sequentially.
Era da tempo che volevo leggere questo libro, viste le ottime recensioni da parte di addetti ai lavori o personaggi “influenti” del variegato mondo della programmazione. Ora che l’ho “digerito” (ci ho messo quasi tre mesi per leggerlo tutto!) non posso che confermare l’assoluto valore di questa pubblicazione! Titolo: The Pragmatic Programmer: From Journeyman to Master Autori: Andrew Hunt, David Thomas Lingua: Inglese Casa Editrice: Addison Wesley Struttura del libro L’opera ha una struttura molto “libera”, i singoli capitoli infatti non sono (tranne qualche rara eccezione) pensati in rigida sequenza.
Today’s book review is about the very interesting, and long-awaited, book from Pramod J. Sadalage e Martin Fowler. Title: NoSQL Distilled: A Brief Guide to the Emerging World of Polyglot Persistence Authors: Pramodkumar J. Sadalage, Martin Fowler Language: english Editor: Addison Wesley (September 2012) NoSQL: beyond buzzwords The term NoSQL quickly became a buzzword, and NoSQL Distilled authors know this very well, so they decided to face this problem - in my opinion - in the best way: give a clear, effective definition of NoSQL and stay with it throughout the whole book; of course they also state that it is their personal and, most importantly, pragmatic interpretation.
Titolo: Don’t make me think. Un approccio di buon senso all’usabilità del web - seconda edizione (2 marzo 2006) Autore: Steve Krug Editore: Tecniche Nuove Ho appena finito di (ri)leggere questo libro, e non posso assolutamente non parlarvene! Si tratta infatti di un testo importantissimo non solo per chi si occupa di usabilità dei siti web, ma tutte le persone coinvolte in qualche progetto di questo tipo, siano essi semplici siti web, portali o applicazioni.