Skip to content

Latest commit

 

History

History
63 lines (37 loc) · 2.84 KB

File metadata and controls

63 lines (37 loc) · 2.84 KB
title Tipsrundan 54
description Time is flying and we're back at Tipsrundan time!
slug 54
authors
hlondogard

👋 Welcome to Tipsrundan! A biweekly newsletter by AFRY IT South with ❤️
Time is flying and we're back at Tipsrundan time!

Tipslådan 🗳


Godisboxen 🍭

🔀 The Apple GPU and the impossible bug The Apple GPU and the impossible bug

Rosenzweig is brilliant! Do you enjoy fun debugging? Join in on Rosenzweigs journey. You'll learn more about GPU:s and rendering including shaders and everything. :)

rosenzweig.io↗

🎒 Using Java's Project Loom to build more reliable distributed systems

Personally Project Loom is incredibly exciting. Green threads without changing your code? Count me in!

Here's a interesting blog about a usecase of Project Loom to test distributed Databases in a more efficient manner. It's pretty technical, so be ready!

jbaker.io↗

📱 How I fell in love with low-js

Every day I feel like more and more the pendulum is swinging towards Server Side Rendering again, not only because of simplicity but also because of efficiency. A Server Side Rendered app is much better as long as we don't require interaction on the client (e.g. Google Slides, Figma and others). A lot of apps today are built as Backend + SPA even if it's not required, slower and buggier. Reducing glue code and having less states (Server Side Rendering) can only be positive! Or can it? What is your take?

edofic.com↗

🔀 Choose Boring Technology

Given the previous post I think this is a given contender - Boringtechnology is a classic which I think everyone should view and think about. If you enjoy these types of thought experiments / ideas, then make sure to join #learn-bokcirkel_south which discuss things like this weekly!

boringtechnology.club↗

🔀 Patterns in confusing explanations

Simply brilliant.

Hello! Recently I’ve been thinking about why I explain things the way I do. The usual way I write is:

Try to learn a topic Read a bunch of explanations that I find confusing Eventually understand the topic Write an explanation that makes sense to me, to help others So why do I find all these explanations so confusing? I decided to try and find out! I came up with a list of 13 patterns that make explanations hard for me to understand. For each pattern I’ll also explain what I like to do instead to avoid the issue.

jvns.ca↗


Thank you for this time see you in two weeks

  • Hampus Londögård @ AFRY IT South