I made this comment on a Zig issue last year and stand by it. Please - make compiler errors as verbose and dumb as they can be if it means I can figure out how to solve the problem quickly.
My time is more important than my ego.
(ofc Zig is WIP so hopefully this'll improve!)
1/2 Thinking of doing something crazy. Normally I don’t accept gifts, but a friend had a Zynq Ultrascale+ that had gone unused for years, and offered to let me use it. To pay it forward, I’m considering donating my Arty S7 to someone who wants to get into FPGAs but cant afford it
Anyone doing anything hard in Unity atm and need any help? ~10yrs Unity experience, UI, ML, DOTS, Shaders, Tooling, Architecture, Addressables, Optimisation etc! RT's much appreciated.
one trick to programming productivity is figure out half of the structure of your program by thinking hard, and then discover the other half from the process of trying to actually write the code for what you've been picturing
Announcing the 2024 Zig Software Foundation financial report and fundraiser!
We're also going to have a Zig SHOWTIME episode where Andrew will present the 2024 roadmap for Zig!
https://t.co/7pjUdGNF6a
I don’t have enough money for flying to Spain to present my research paper.
If you are not aware, me and my friends have been working on ElysiaJS research paper for almost a year.
Got accepted and going to be presented at SAC.
But I don’t have money to get there.
Uncle Bob's "Clean Code" is the Strunk & White "Elements of Style" of software dev.
The less you understand the craft, the more helpful it seems. Once you understand the principles of the craft, you can clearly see it is toxic brain poison that can take decades to unlearn.
Zig might be the most ambitious language we’ve looked at on Developer Voices - it’s trying to replace C, compete with LLVM and be the foundation of the whole compilation story. It’s a feast for language fans…
🎧 https://t.co/UmRnK0alIv
📺 https://t.co/5zHUGY01WK
@Madisonkanna As someone who works full-time in C, I will say that a lot of the traditional educational material around learning C is not very good, because it was made in such a different hardware landscape. Programming in C today is so different (and better) than how it’s normally taught.
ok i'll elaborate bc this is my love language
SOLID: this is most obvious one. srp leads to excessive classes or functions, which increases overhead of calls or object creation. say we have a class for a user and another for an address. a user has an address. in a conformant design, we would have two separate classes. each time we create a user, we would also need to create an address. this means two object creations and potentially two database calls. open/close, liskov, interface segregation, and dependency inversion all introduce potential bottlenecks with virtual function calls, dynamic dispatch, and/or object creation.
KISS: this is usually great and can even be good for general performance. but sometimes solutions require complex, optimized code. a linear search in an array is easier to understand, but a binary search or a hash table lookup is way faster for large datasets. not to mention the perf benefits you might get from manual memory management, parallelism, bit manipulation, etc... none of which are "simple".
DRY: i generally don't follow this anyway. repeating yourself is fine ¯\_(ツ)_/¯ i find it much more tedious to understand an over-abstracted catch-all function than seeing some duplicate code. with performance in mind, knowing the constraints of the problem you're working means you might be able to get huge boosts from writing similar but slightly different functions tailored to the problem, unrolling loops, or creating one-off variations that solve performance issues in certain parts of your code.