CR @creative_coder
Showing posts older than #832 · Back to latest
Forwarded from xynapsy
YouTube Coding Adventure: Software Rasterizer Let's try to turn some dot products into a 3D world! Support my work (and get early access to new videos and source code) on Patreon or Nebula * Patreon: https://www.patreon.com/SebastianLague * Nebula: https://go.nebula.tv/sebastianlague Source code: *…Forwarded from Volodymyr Agafonkin
Forwarded from Yuri
Forwarded from O Popov
Forwarded from Yuri
Forwarded from Yuri
🧵 Thread • FxTwitter Tim Soret (@timsoret) This isn't getting enough attention. Rive has solved vector feathering! The blur isn't a costly post-process convolution, it's mathematically pure at the vector level = incredible performance even with ultra large kernels. Incredible work from @csmartdalton…
– Always prefer simple solutions
– Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality
– Write code that takes into account the different environments: dev, test, and prod
– You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested
– When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we don’t have duplicate logic.
– Keep the codebase very clean and organized
– Avoid writing scripts in files if possible, especially if the script is likely only to be run once
– Avoid having files over 200–300 lines of code. Refactor at that point.
– Mocking data is only needed for tests, never mock data for dev or prod
– Never add stubbing or fake data patterns to code that affects the dev or prod environments
– Never overwrite my .env file without first asking and confirming
Forwarded from Yuri
Forwarded from Yuri
