HNHacker News
TopNewBestAskShowJobs

cookieperson

375 karma · joined December 29, 2021

submissionscomments
cookieperson··on Clever code considered harmful
I hear you, that's why I said "most". But there's also a flipside where someone tries to tweak a language feature or implement a missing language feature with an inhouse macro. That macro goes on to be defunct but a major chunk of mission critical code is now glued too it. After all we can't expect languages to not fill in missing gaps in an opinionated way. The only way out is to wall off a code base for a month for a treacherous refactor.

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.

cookieperson··on Clever code considered harmful
I think if you took a survey about which code is easier to read a pile of expressions acting as closures inside of nested method calls or a loop, you would likely find most programmers have comfort with one over another. That's objective because it's how pseudocode, the most widely used language agnostic abstraction used in computer science beyond plain text, is written. But that's really not the point and it never was, right?

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.

cookieperson··on India ruling party's IT cell used AI to show smile on arrested protesters' faces
The problem with all civil rights movements is, any ground gained can be easily removed later. Technology like this is almost the perfect tool for doing so. Buckle up it's not going to be pretty.
cookieperson··on Why I Left Rust
Julia doesn't even operate in the same space as rust... Julia is closer to go lang than it is to rust and I wouldn't say those two languages are similar at all. Also if I were picking a language on community alone, I'd pick rust. The issues going on here are not reminiscent of the community at all. Julia also had drama over conferences and allowing members to speak...
cookieperson··on Clever code considered harmful
It's a good thing I didn't say "don't do X"
cookieperson··on JeanHeyd Meneide's response to “Why I left Rust”
The people who seek out these positions are almost always doing it for their egos. If I had to guess based on my life experience the ones jumping ship are in the other camp.
cookieperson··on Clever code considered harmful
Ignoring rust or any language specific thoughts... Sure, but there are many cases where it's still better to have slightly slower code at the expense of readability/extendability/maintenance. Even in HPC applications. I know I know some very smart people are about to throw their sharpened axe at me. But in my experience very rarely does someone truly need to sacrifice a bounds check to deliver their product or save meaningful amounts of $ in prod. Not saying all loops must be bound checked, that's a dumb hill to die on. But I've seen devs hyperfocus on hypothetical minimal gains that get blown away two days after the code lands, or a minor requirement changes.

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.

cookieperson··on Landauer's Principle
How much energy do you spend cooling your quantum computer?
cookieperson··on Clever code considered harmful
Sorry to hear that. I'd pitch to invest in the teams education a bit. A little time spent establishing some ground rules goes a long way. If it's your boss biting down on you for it, don't waste your time, seek a new environment if it bothers you or stunts your growth. Most code review cultures degrade into absurd rules over time because of human power structures and crappy feedback loops. I'd imagine if some of those things became rules either there's an obscure reason for it, or the environment has rotten out.

I've seen both cases for some of these types of things. The rotten culture being the most common

cookieperson··on Clever code considered harmful
If you look at golang... It's entire purpose for existing(in my opinion) was google realized it had too many people who couldn't be trusted to write maintainable code with all of the flexibility of most programming languages. And yes, google hires many of the best and brightest, and yep go lang is still flourishing despite being an objectively rough language.

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.

cookieperson··on Clever code considered harmful
Pretty sure 99% of the world agrees with you here. If someone wants to write twenty nested closures that compose some category theoretic construct in some ancient academic paper instead of two function calls using an already imported library they can go to their museum or whatever to be studied. The rest of us have shit to do...
cookieperson··on Clever code considered harmful
If a code reviewer pulls that on you, meet with them and explain why that's asinine. If that fails bring in someone more senior as a tie breaker. If that fails, find somewhere else to work...
cookieperson··on Clever code considered harmful
I don't think most people would describe almost anything you wrote as clever. I hope that's not insulting...

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.

cookieperson··on Production AI systems are hard
I'm not scared of AGI beyond how it's likely lead to societal collapse because of human greed. I am worried about the operationalization of the current chat bot technologies and other generative AI modelling techniques for harm. You don't have to have a smart system to hurt hundreds of millions of people.
cookieperson··on China state-sponsored cyber actor living off the land to evade detection [pdf]
All of the recommendations I saw were based on windows
cookieperson··on The Future of Consumer SBCs: Has the Pi Bubble Burst? [video]
I know that's why I said I was being a turd sandwich.
cookieperson··on Ask HN: Is Rust worth investing in as a reliable C-alt given its recent saga?
Yes absolutely. The politics is stupid crap. If everyone in the rust org quit the community would continue onwards just fine.

Rust is a great language with a lot of advantages and is absolutely worth considering for your next project.

cookieperson··on The Future of Consumer SBCs: Has the Pi Bubble Burst? [video]
NUCs are great but they are often completely overpowered for a given application. The additional 200 you drop for it isn't worth it. Also 30w may be chips for a PC, but for battery powered or hybrid powered applications it's a lot of load.

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.

cookieperson··on The Future of Consumer SBCs: Has the Pi Bubble Burst? [video]
It seems so wrong to use python in embedded but I know that's me being a turd sandwich.

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...

cookieperson··on Rust: The wrong people are resigning
Might be interesting to make it completely democratic so less inside recruiting happens. Using ranked choice community wide voting with fill ins. Otherwise stuff might rot from the inside...
cookieperson··on Rust: The wrong people are resigning
If there's one thing I've learned from most of this it's that paying attention to the people in charge is probably not worth the effort. They come and go, lots of drama, and insiders are reporting the ones who are there probably shouldn't be.
cookieperson··on Rust: The wrong people are resigning
Go to HN page 2 and grep for Rust. More drama with the rust governance or something. They gave someone a professional honorific and took it back for unstated and less then satisfying reasons. The person it happened too seems to be a good enough person and some nice people left the rust org over it.
cookieperson··on Rust: The wrong people are resigning
Fasterthanlime is something like my spirit animal. Prolific and educational blogs that have challenged my knowledge with whimsy joy and catharsis. Also apparently emotionally intelligent and making the right moves here.

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!

cookieperson··on China state-sponsored cyber actor living off the land to evade detection [pdf]
It's a less interesting target for a lot of widespread attacks. Consider the surface area of Linux machines vs Windows? Most big corporations run on windows, even if devs rock Linux, that's not usually what these types of attacks are after.

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.

cookieperson··on China state-sponsored cyber actor living off the land to evade detection [pdf]
Oh for sure. Just saying in this specific bulletin there's no mention of Linux or macos targets.
cookieperson··on China state-sponsored cyber actor living off the land to evade detection [pdf]
Not a single mention of Linux. Hope the windows community comes together and finds ways to harden these exploits
cookieperson··on Why I Left Rust
Weird thanks for filling me in. Uh yea I had no idea... Ferris is the little crab right?
cookieperson··on Why I Left Rust
What is the deal with trademarks and rust? See a lot of people talking about it...
cookieperson··on Why I Left Rust
People often get time off of work or school to be honored with formal talking gigs. IE your boss will let you off the hook to prepare for it because it makes your company/school look good. It'd be pretty embarrassing to have to explain to your boss or your PI that "oops I'm no longer a key note speaker"
cookieperson··on Why I Left Rust
Also you are allowed to call that out AT THE CONFERENCE. In my field conference talks always have a Q and A. Sometimes people get completely shredded (in a tactful professional way) during a Q and A. If it's something you disagree with ask questions. This is someone willing to put their reputation on the line to say something, they've been vetted, voted on, made arrangements, etc. If they are wrong well that's what peer review is for, and working as a team is for.
← PreviousPage 2 of 8Next →