Jakub Marchwicki

Jakub has been around software development for past 10 years, wearing multiple hats, getting hands dirty in multiple environments, securing both technical as well as the business side of The Thing. “An engineer with a human friendly interface?”. Some languages, some frameworks, blah blah blah - doesn’t matter. Jakub always considered programming as a tool to solve real-life problems - in a pragmatic way. He always stayed closed to business side of the solution, still focusing on the technology. He combines daily job of managing a horde of software engineers at Young Digital Planet with lectures and technical trainings and comittment to Gdańsk Java User Group.


In English 6 tips for you JavaEE project be less depresing

People are stuck to JavaEE not because they love it, but because it was in their work place, it is still there and will be there long after they leave. While many engineers think about going reactive, functional (or any other fashionable buzzword), some are still struggling how to migrate weblogic9 to weblogic12 and move from Java not supported for past 8 years (like Java 1.4) to the one not supported only just for a year (Java7). While their live can be miserable - there are means for them to win JavaEE back, have fun again. It still won’t be a super duper modern framework, it won’t have all the latest pre-summer goodies, won’t be a sweet language (full of syntactic sugar candies), but a solid set of tools that can make development pleasure again (kind of). In the modern JavaEE you are no logger limited to the 'standard' but you can take advantage of limitless set tools and libraries. For some people it will still be the bad and ugly JavaEE, "feels like Spring but n-years ago", "Spring wannabe in the poor’s man land" - that’s true. But if you can’t win Them (and let’s be honest - in most enterprise’ish environments you can’t win Them), join them! And have you JavaEE the way You like it. This presentation will walk through multiple libraries that can help you change your project from "This is The Standard Even If It Doesn’t Fit" way to a something far more approachable, where your tools doesn’t feel like the Maslow’s Hammer. I’ll be sharing some experience from multiple trainings, projects and refactorings of old-but-still-in-production JavaEE applications and tools we used to get away The Standard.

In English Asciidoctor 101: Chasing Gods of Technical Documentation

One of my professors at the university used to say: "Developers are paid for writing docs as they write code for pleasure". However the reality differs, documentation is the last thing we want to think about. It’s boring, in MS Word, in a different workflow than code, with no transparency between 'commits' whatsoever. My intention for this session is to show opposite, that there is a 3rd way - as easy as writing an email, a memo; like a few lines of code. At least that’s an idea behind AsciiDoc (or Markdown or RestructuredText) - simple, intuitive and minimal syntax, text based documents, readable without additional tools. During the session I’ll introduce AsciiDoc (and the tools ecosystem around it). Above all, I’ll like to share a passion for better writing, with simple tools, easily sharing outcomes of our work. Step by step we will be tackling the syntax, tools - in possibly the most pleasant way - writing live. I’d like you never ever go back to Word! Because it’s beyond WYSWIG editors when writing becomes simple and geeky-pleasure.


You like this speaker?
Share with others!