I am pro have fun screw up and grow. But macros present a certain kind of danger a lot of other tools don't. If you are playing with them be careful of their scope is my only real warning.
375 karma · joined December 29, 2021
I am pro have fun screw up and grow. But macros present a certain kind of danger a lot of other tools don't. If you are playing with them be careful of their scope is my only real warning.
You can grill me if you want and say I am the problem! Zing ouch got me so good! Those HN points will get racked up, so much winning...
Or you can read between the lines. I drew an unspecific example with microseconds of thought behind it. People who know what I am saying know what I conveyed is fine. People who know me, know I regularly use pipes and chained method calls all day. The point is, the paradigm could go either way, it depends on culture(reading the room), and design decisions. Had I of flipped my example and said "method calls can make code way cleaner than for loops" which in some contexts is equally valid your antiparticle HN contributor would make the same argument you made calling me the problem. Get it?
I would say people trying to shit on everyone around them for being casual are more of a problem then anything else. Especially in collaborative development environments. That supercedes any code anyone could contribute. But that's my take and I'm not going to suggest it belongs on some arbitrary list of ad hoc HN rules (of which none hold water)... I won't be writing a five pager with examples where what I said was sound valid and best praxis, I have nothing to prove, and that was never the point. Everyone who knows what I'm talking about gets it. Happy flag planting with imaginary enemies.
The challenge with DO NOT TOUCH this code comments that intense performance tuning leads too(figuratively and literally) is it makes people who don't understand the code build bizarre(and often slow) monuments all around it that don't usually need to exist and deter from the minor gains won over a cute optimization. I've seen this happen ALOT.
Of course there are times where you should opinionate your code to better serve the machine. But my big thing is, it's rarer then the overly complex design decisions favoring it are and compilers are getting better every day.
I've seen both cases for some of these types of things. The rotten culture being the most common
I'm with you though. I don't like reviewing a lot of code because it sucks calling out a simpler approach to someone who is clearly trying to showcase their greatness. Can put mid level engineers who know better in a crappy spot.
Metaprogramming tho... You want to make a magic black box that takes hours to debug and conceals real bugs, invest heavily in metaprogramming to save a hundred lines of code that can be maintained with three find and replaces/SED calls and a recompile a year... Most metaprogramming shouldn't exist in production code.
Programming is social. You have to weigh your decisions heavily by who you work with now and who you might work with in the future. If you work in a niche language or toolset you might think "this is my chance to do whatever I want!" But the reality is, it should be the complete opposite.
Most compilers make clever code silly. You can write a 15 line hard to read pipe or method chain, or a 25 line double for loop with the same runtime characteristics. The latter is always better to maintain, while the former is always more clever. One is good for the team the other for someone's self esteem.
Rust is a great language with a lot of advantages and is absolutely worth considering for your next project.
Where NUCs become very attractive in my opinion is when you need reliability. Rpis are cute, but anyone who has ran one consistently for 6months has likely had some sort of issue. Bad SD card, random restart, or what have you. Most NUCs will not do that to you. But there are also other SBCs with a price range in between that wont either.
But I do have to admit, arduinos and rpi zeros are in the same price point. I don't blame people not needing analog for going rpi even when it is gross overkill.
I'm just a minimalist. If I can do my project with 16kb of RAM, I'm not going to throw a GB at it.
That all said... This article is silly. No raspberry pis aren't popping or something. The biggest complaint I think most people have with them is you can't buy them anywhere. Constantly sold out. I would have bought two or three this year otherwise...
Sometimes it's better to drop out and start something new. An unofficial convention would be fantastic.
I'm sick of the clout chasing in these niche tech areas, it always drowns out the real passion and all the fun. The passion that fosters a healthy community and technological success.
Sometimes I wish a personality test was common for these ad hoc governance type positions (not just rust but with any OSS software). Not to exclude people but to decide if things are balanced. The people who want nothing to do with these systems often should be the ones figuring it out, but the people leaving trails of bodies behind them to plant their flag should be nowhere near them.
Thanks for sticking up for the people resigning and framing the bullshit in a realistic way. Also thanks for staying positive and I hope you keep blogging!
That said you are right. Most Linux users ride on insecure machines. I remember talking to someone who had no idea they had to set up a firewall. They had switched from Linux 2 years prior under the guise that it was more secure than windows out of the box. I wish Linux security was talked about more. The people who know how to do it assume everyone does, and the people who don't... don't know what they don't know.