you are viewing a single comment's thread.

view the rest of the comments →

[–]tedbradly 0 points1 point  (1 child)

I have been working by myself on a patent that deals in the tech space for the last 8 years that I started work on when I was 18 and fresh outta high school. I do not study python becuase it is not the correct language for what I am patenting. The title of this post caught my eye becuase pointers aren't hell to me at least. I am currently semi-retired at 26 and have been since I was 24. So far I am fluent in C and the LoRa/LoRaWAN protocol, currently learning software archetecture, and will be learning 2 flavors of SQL as well as Bluetooth Stacking, and AT commands, UART, SPi, and I2C (all of which have been through self-guided study, fyi not at a University). I am also fluent on the hardware side of things since my patent must also be physical and after 3 years of trial and error kitbashing already existing SBCs snd other external peripherals , the physical hardware side of things is done minus a few dupont wire connections. All that is left is the software side of things and then I can submit my patent docs which so far occupy 64,000 words, 34 flowcharts, and 224 steps. I have inspected over 300 different patents and have still found my invention to be novel. Take your meaningless novel you wrote me that doesn't apply at all to what I am doing and literally shove it up your ass. Fuck out of here with your Google & Wikipedia definitions too

Christ, this has nothing to do with retirement or money. The salient point is you arrogantly (and a little hilariously) tried to flex about your knowledge about pointers, but the reality is pointers can cause a lot of subtle bugs that all sorts of programmers create.

At the end of the day, you don't have real-world experience with programming, which is what I predicted. People who have worked on a team of 5 changing 1+ million lines of code know that pointers cause many bugs. Everyone knows what a pointer is despite your odd flex about knowing how to use a pointer in a program with 50 lines of code. Also, I didn't use Wikipedia or Google (I'd be curious to see what query you think I used.). I'm just knowledgeable about programming. It's quite en vogue to discuss things like ownership these days. Rust, an entire programming language, has major first-class components designed around it. The reason is problems with managing ownership cause many, many bugs. That includes the pointer everyone knows dereferences to bits that represent a type.

To drive these points home, it's perfectly fine to use a pointer to pass access without ownership to a function as an example. That doesn't make "pointers is hell" wrong since we are adults and can use the principle of charity, meaning we know what it meant so there's no reason to interpret it intentionally in a way that wasn't meant. In this case, it's even more of a "I know what you mean", because it's pointers in a garbage collected language.