Urgent.News

What's breaking now, across thousands of outlets.

Tech

meu primeiro teste: LuizaLabs

Há um tempo, no início da minha trajetória como desenvolvedor, fiz o teste técnico da LuizaLabs — foi meu primeiro contato real com um processo seletivo na área. O desafio era ler um arquivo de log de partidas do Quake 3 Arena , extrair estatísticas de cada partida (jogadores, kills, mortes causadas pelo próprio jogo) e expor isso por uma API — com testes automatizados e, se possível, algo além…

Original Portuguese Read in English

No beginning of my developer journey, I took the technical test of LuizaLabs — it was my first real encounter with a selection process in the field. The task required reading a log file of Quake 3 Arena matches, extracting statistics from each match (players, kills, self-inflicted deaths), and exposing this data through an API, including automated tests and an enhancement if possible.

I decided to revisit this project now and document the logic and decisions I made at the time, both as a personal record of that phase and for anyone facing a similar challenge today.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Docker vs. Kubernetes: Which Should You Learn First?

Docker vs. Kubernetes: Which Should You Learn First? This question comes up constantly, and the honest answer is that it's not really a choice between two competing tools — it's a question of…

  • Docker packages applications into portable containers.
  • Kubernetes orchestrates Docker containers across clusters.
  • Docker is sufficient for small-scale applications, Kubernetes needed for scaling.

The Logging Dilemma

Every developer has lived through this scene: the adrenaline spike when a production incident is announced. That mix of dread about what you are going to find and frenzy to collect any piece of…

  • Logging dilemma causes frustration for developers during production incidents.
  • Team reduced log level to avoid debug log flood, but lost crucial context.
  • Dynamic per-operation log level implemented to balance information retention.

More from Monday 14 September →