Julius Rajala

Julius Rajala

@dvergmal.dev

I’m an amateur cyclist, sailor and dungeon master. Working on the friendly approach to developer productivity. https://dvergmal.dev

78 followers104 following49 posts

Julius Rajala
@dvergmal.dev

A bit of over two months in a product focused software startup has done wonders to revitalize my interest in working in tech. I’m considering picking up writing about engineering but what sort of topics are people reading outside the LLM hype?

Julius Rajala
@dvergmal.dev

I forgot to post about this but I scratched together some in-browser character sheets for #dungeonworld. These work pretty decently for a low effort one-off sessions.

Julius Rajala
@dvergmal.dev

I think the time is ripe for a social network where users have to authenticate to prove they’re human. A system based on identity brings accountability and makes it harder for hostile actors to influence. The EU seems like the best location to kick off something like this but can we deliver?

Julius Rajala
@dvergmal.dev

One thing I’d like to see one day is a viable competitor to event organization for Facebook (back in the day). Getting people together for events leaves my whatsapp snd telegram riddled with small groups and Fb used to work well for this. On #atproto would need for private audiences.

Julius Rajala
@dvergmal.dev

#atproto #developers question: If I develop an application based on the protocol, is there a way for me to prevent the data from being discoverable or is everything fundamentally discoverable by anyone? I’m wondering the plausibility of only publishing content to a users followers/following.

Julius Rajala
@dvergmal.dev

Probably need to force a little switch in thinking here. I’d like to build data-types that extend the formats used by Bluesky. Create a post on #atproto that’s visible on bluesky and show some extra info on another platform? #developers

Julius Rajala reposted

Bluesky
@bsky.app

Brief update on our ongoing efforts to allow users to specify consent (or not) for AI training: 🧵

Julius Rajala
@dvergmal.dev

I’m at the halfway point of Twenty-four Days of Software Consulting. 📅 Since Friday, there's new posts about adopting new technologies, project documentation, refactoring codebases and today's post regarding mentoring. ⭐ Check out todays post about mentoring here! twentyfour.day/s/of/consult...

twentyfour.dayTwentyfour.days - What strategies do you use to mentor developers?Twentyfour.day is the Corporate Software Engineering version of a beer advent calendar.
Julius Rajala
@dvergmal.dev

I learn via building things. Admittedly, I don't build toy software quite as much as I've used to, but I do still like to to learn new things via doing. This project is a brief intro to Astro on its own.

Julius Rajala
@dvergmal.dev

If your team does sprints, pick items from both maintenance and feature backlogs. If your development is pull-based, make sure you provide some priority to balancing these. Pick both.

Julius Rajala
@dvergmal.dev

There’s a delicate balance, where time has to be secured for both. The clients business value often comes hand-in-hand with new features, while maintenance is a must to keep the current users content.

Julius Rajala
@dvergmal.dev

A personal favourite for me has been reserving one day in the working week to technical debt and refactoring of the hairier bits in projects. It can sometimes be difficult to justify this timespend to the client, but it helps to outline the accruing costs down the road that might follow.

Julius Rajala
@dvergmal.dev

Selecting a stack for a project can be tricky. There's often no single solution to solving any problem. Often, boring technology is better than exciting in the long run. What I think matters most is confidence in the selected tools, from both the perspective of the development team and the client.

Julius Rajala
@dvergmal.dev

Selecting a stack for a project can be tricky. There's often no single solution to solving any problem. Often, boring technology is better than exciting in the long run. What I think matters most is confidence in the selected tools, from both the perspective of the development team and the client.

You are up to date.