One way of solving this is to structure all of your nodes into a HashMap with the node ID as they key and the node type as the value. The underlying node type could have node IDs for referencing purposes. You lose the ability to reference the parent/child/sibling directly, but you avoid direct circular dependencies. That said, now you need to manage dangling references for when the node is removed from the main HashMap collection.
For me it all depends on how often a project changes. If it’s constantly in flux, I don’t bother remembering any of it because I might not be the last one who touched it. The more you try to remember everything, the more wrong you become due to the successive work of your coworkers.
“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.” -coworker standing atop the Dunning-Kruger peak
There are so many ways to be a hero for those around you. Why end your life when you could dedicate your life to help those in need? When you feel at your lowest, remember that there is someone, right now, who wants to know and believe in you and who hopes that you could do your very best to help them and others.
This is intended to be motivating. Instead of leaving a hole in the world, you could become a role model for others.
I hate that it came to this, after so many Rust devs left, but all I can say is “Good.”
It happened to a friend who wasn’t passing in the proper types into their stored procedures, all strings, and “null” (not case sensitive) conflicted with actual null values. Everything in the web interface were strings, and so was null.
For some people it takes this mistake before they learn to always care about the data types you’re passing in.
Great list! I would just add The Majority Report if you’re looking to learn more about politics while also trying to understand what is happening today. They do a ~2.5-hour live show every weekday which includes a quick overview of the latest headlines for today, an interview of someone with knowledge about some politics-related topic, and then an hour of mostly right wing videos that they discuss, argue with, and vent about.
I love it for how informative it is and for keeping me sane.
At first I was disappointed to see this, but after looking into it it looks like they weren’t using hyper as a means to migrate the project to Rust. If they’re not going to move away from C, it seems like a fair decision.
One way of solving this is to structure all of your nodes into a HashMap with the node ID as the key and the node type as the value. The underlying node type could have node IDs for referencing purposes. You lose the ability to reference the parent/child/sibling directly, but you avoid direct circular dependencies. That said, now you need to manage dangling references for when the node is removed from the main HashMap collection.