Last weekend Squeed once again hosted an internal hackathon were we had the opportunity to meet up, exchange experiences and code together! During the hack we talked a bit about testing in Java and how nice it would be to have instant confirmation about the status of your tests. None of the participants in the […]
Den 18:e september delar Squeed med sig av sin kompetens för fjärde gången på JavaOne. JavaOne arrangeras av Oracle och är världens största Java-konferens. I år har vi tre talare på plats som presenterar:
Ett tips på hur man kan hålla sig uppdaterad på trenderna inom mjukvaruutveckling är att lyssna på en välproducerad podcast med bra bredd. Och ett tips på en sådan är Software Enginering Daily som håller hög kvalitet, intervjuar många intressanta personer och har en fantastisk bredd på sina ämnen.
A week ago the second edition of the Java Barcelona Conference took of in the catalan capital. With an ambitious schedule of 8 workshops and about 50 talks, spread over four different tracks over three days, a weekend with a lot of Java and JVM-related knowledge-sharing began. The conference attracted about 300 developers who met up at the facilities of the University Pompeu Fabra. As I was there to speak about Reactive Java EE I had the opportunity to experience the conference both as a participant and as a speaker.
At thursday evening the speakers dinner was held at the sport harbour of Barcelona. The organizers Barcelona JUG did an excellent work in welcoming us to their city and with a great view, great tapas and with even greater company the speakers shared a really pleasant evening. It was a true privelege to meet passionate people with
When I went to university and started learning to program I spent a lot of my free time making games from scratch, I wanted to apply some of my physics knowledge in making game engines. I started off with making a space simulation game and implemented movement based on Newton’s law of motion, gravity was affecting the ships and I made them able to shoot bullets. However, the engine proved to become more difficult to program the more features I added, I wanted collision detection, support for multiple players etc. and finally ended up in scrapping it all together due to design flaws and the engine being way too complex to keep together without introducing bugs all across the board. I did not give up, though, and ended up restarting from scratch multiple times bringing knowledge of my mistakes to the next try. My point being that reducing complexity in software design is not something only the most senior software architects need to address, it is among the first
A couple of years ago I worked in a project with a Python backend. As I had only used python as a script language before I soon grew to really love the powerful interactive console that let me explore and learn the language (and which saved me a few hours of debugging every week). The interactive console is the thing I miss most when I’m in my Java codebase, but fear not, with JDK9 we as Java developers will also gain the benefit of a REPL!
If you have 3 minutes over, take a quick look as I scratch on the surface of JShell
JDK9 is out in early access so check it out!
Over n out
One word that sends shivers down most developers spines is ‘Legacy’. There are many different kinds of legacy-systems and obstacles that they impose. Legacy exists on a scale; on one end there are systems that you don’t want to touch because no matter what you do, they will most likely implode. On the other end there are systems that only have been mistreated code-wise or architecturally but actually have some kind of potential and can be refactored iteratively and improved upon. Some legacy-systems could be at their end of life while other will continue to live for a long time.
Not so long ago, i was a part of a team that got a legacy application assigned to us. This legacy-system was probably somewhere down the middle on the ‘legacy-scale’ and there were no plans to replace it. The perfect victim for some refactoring and improvements! Not only for the sake of the system but for the sake of the developers that are going maintain the application and introduce new features.