Tadas Šubonis

Intro Recently, I’ve realised that a lot of newer developers and information workers in general haven’t realised that the availability of LLMs like ChatGPT and Perplexity has changed expectations for what “good work” looks like.

A general overview and introduction to Scrum for junior developers that haven’t done this before.

Intro A goal of this write-up is to introduce the main tools of domain-driven design to new developers so they can pick up the approach quickly.

About This post collects the technical, code-focused tips that help new developers write maintainable software fast.

About This post is intended to get new developers up-to-speed quickly on the best software engineering practices.

About This post collects the working-culture tips - communication, task management, and process habits - that help new developers become productive members of a team.

Intro This is a quick and rough introduction for fresh developers to RESTful APIs.

Intro Recently, I was looking to find a good working example on how to create a custom Spark SQL User-Defined-Function (UDF) on Java on build that using a modern tool like Gradle.

During my years as a software engineer, I got exposed to more and more data-based projects where data engineering and model research were major aspects of the system.

Intro In my opinion, it wouldn’t be outrageous to claim that tests are the most important part of the code you write.

Intro A while ago I’ve wanted to bump up non-existing gaming and deep learning capabilities of my workstation.

Due to strange reason lots of people take Object Oriented Programming and Functional Programming as mutually exclusive paradigms.

This is a continuation of the first part but while in the later I’ve focused more on the whole industry, this time I’ll try to reflect on how my own software development practices changed over time.

It’s a new post to this almost-abandoned blog.

Initially I’ve posted this on Goodreads but I think it’s worth cross posting here :).

For some time I have been thinking about game development.

Getting current time in the system .

I often see people falling for the trap of “Transactional scripts” so I decided that it is probably worth writing about this so more programmers would be able to identify flaws in their design and improve.

It’s usual practice to validate all kind of data in software engineering.

A while ago I presented lightning talk at LJC about Domain Driven Design.

Just recently I was in the need to set up continuous integration for OSS project that I am working on right now (DDocumentor) and I found that that drone.io others great free service for open source projects.

As I stated a little bit earlier I am not really fond of writing stuff about some specific technical topics but probably I’ll start doing exemptions.

Recently, when I attended Adopt OpenJDK test fest, I found good examples of test writing cases how NOT to do it.

This time I decided to cover interesting topic about integrating subsystems using EventBus.

As you remember in previous part we talked about some OOP technical stuff that helps us make better software.

For a while now I have been noticing people saying that they are doing OOP but instead they are actually programming in procedural style.

Recently I was interviewed at the very first stage with codility.

I will begin my dev blog on Google platform by post why I am using Java.