←
Pal Szasz248 posts
Pal Szasz avatar

Pal Szasz

@space42
◷ Joined March 2009
Sebastian Aaltonen avatar
⟳ Pal Szasz retweeted
Sebastian Aaltonen@SebAaltonen·8 Jun 2022

At Ubisoft/RedLynx (2015) we developed a new ECS system for our new engine. It had super nice query API. The implementation was a massively complex variadic template monster. Only a few people in the studio could maintain it. Debugging it was hard. Compile time slow. Thread...

Sebastian Aaltonen avatar
⟳ Pal Szasz retweeted
Sebastian Aaltonen@SebAaltonen·18 May 2022

At HypeHype we are pushing unfinished features directly to dev branch behind feature flags. This improves iteration time compared to long lasting branches, and avoids regressions when people land their long lasting branches at the same time (never cross testing them).

Horthic avatar
⟳ Pal Szasz retweeted
Horthic@Horthic·15 Nov 2019

Baptiste mains when they see a teammate dying across the map:

0:10
Stylosa avatar
⟳ Pal Szasz retweeted
Stylosa@Stylosa·6 Aug 2019

#videogamesaretoblame for: ✅Helping me in my darkest hours deal with chronic illness. ✅Giving me a job. ✅Taking me all over the World. ✅Allowing me to entertain millions. ✅Changing my life. What about you?

Post attachment
I Am Devloper avatar
⟳ Pal Szasz retweeted
I Am Devloper@iamdevloper·5 Jul 2019

being a programmer and watching someone "hack" a computer on a TV show is like being a nurse and watching someone in a movie take blood with a carrot.

Sebastian Aaltonen avatar
⟳ Pal Szasz retweeted
Sebastian Aaltonen@SebAaltonen·1 Jan 2019

Unknown object life time or owner is a code smell (ref count, shared_ptr). In most cases you should be able to define a clear owner for each object. In multithreaded environment custom destructors are very dangerous with ref count schemes. Hard to know when destructor is called.