Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem) header
Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem) profile picture

Prev. Intern at W7-x, CERN. Soft bunch of dragons, advocating for nuclear energy, caring for the world @TheLucidragons@bsky.social

Leibniz University of Hannove
Joined September 2019
Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)Photo by Xasin (@xaseiresh@fosstodon.org) (@XasinTheSystem)
I rly be animating wtv these days tbh
276
15,832
213
128,234
2,119,760
today is a huge day for open hardware. v1.0 of FreeCAD encompasses tremendous improvements across the board. if you haven't tried FreeCAD in a while, now is the perfect time to dive in. congrats to the team on such a huge effort coming to fruition!
1
11
107
5,487
I've mentioned before, but I think about this a lot. "There must be another room, somewhere down the hall, where the real meeting is happening, where the real experts are, making the real decisions ... because it can’t just be us. It can’t just be this." -- Jake Sullivan, 2013
62
726
55
12,217
603,692
Apparently we’ve learned nothing about aggregate statistics obscure how working class people experience the economy. So yes, the wreckage of 50 years of neoliberalism:
“The wreckage of fifty years of neoliberalism”
61
1,512
64
6,950
491,466
Glowy monster!
3
31
294
4,421
How to quickly refollow people at the other place.
184
9,813
420
40,649
2,721,447
Today, my PC was nearly compromised. With just one click, I installed a malicious @code extension. Luckily, I was saved as my PC doesn't run on Windows. Hackers are getting smarter and aren't just targeting beginners. Here's how they do it and how you can protect your coins!
193
1,629
309
10,026
2,517,323
Saying Nuclear Energy is too dangerous to use is one of the most toxic, misinformed, and damaging lies ever spread. Millions of people have died in the decades since invention of nuclear that would've been happy and healthy without coal fired plants. Time to Build
34
201
12
1,093
47,482
On this day in 1938, England's prime minister Neville Chamberlain returned home from Munich declaring there would be "peace in our time," thanks to the deal he and his French counterpart Daladier had just signed with Adolf Hitler. They believed their negotiated compromise (handing over part of Czechoslovakia to Germany) would prevent the West from being drawn into a larger war. They trusted Hitler's handshake. In March 1939, Hitler seized the rest of Czechoslovakia. The war they'd feared came, but later and worse. Today, Western leaders' hand-wringing response to Russia's 2014 and 2022 invasions of Ukraine, with constant wishful thinking of calls to "negotiate" and "avoid escalation" (on one side only, their own), carries depressing echoes for those who remember the lessons of the 20th century. Russian chess master @Kasparov63 is among the clear, articulate voices commenting on the present situation; I recommend anyone concerned about Europe's future to follow him. The memory of 1938 is especially vivid in my family, because my dad (age 7) and my grandfather--fleeing Austria as refugees from Hitler--happened to take the same train as the French prime minister, Daladier, returning from Munich. They arrived in Paris Gare de l'Est to see him greeted by a cheering Parisian crowd, grateful that peace had been achieved. A year and a half later, my dad experienced the effects of war directly when Germany attacked and occupied northern France, where he and his aunt had settled as refugees. The extra time Hitler had been given to plan and build up his military forces--beefed up by resources from the newly seized territories--resulted in a shocking, unexpected French defeat, followed by a protracted four years of the world war appeasement had failed to prevent. #IStandWithUkraine
33
146
10
651
48,650
It's so crazy because vietnam just had a massive cyclone smack into the entire north of the country and volunteers immediately began assembling see through MREs which also contained bandages, shampoo, disinfectant, beer, cigarettes, and a lighter and the police began using...
Police guarding grocery stores while folks are denied the opportunity to purchase baby formula after losing everything is pretty indicative of where we are as a country.
127
10,707
204
90,579
3,678,809
Right , who's ready for some good old fashioned claw envy? Remade epsilons overkill murder mittens to use flexible silicone wire for the lighting. Should last longer than the last ones for sure
4
50
2
440
15,595
Hit us up at the upcoming #Eurofurence for this selfmade sticker design :D Printed on PixieDust glitter backing from Stickerapp for that extra sparkle~, and it's the new logo for our Synth Fursuit project!!
1
6
381
However, the average hides really interesting data. There were no significant decreases in employment status and hours worked among childless adults or those over age 30. It was single parents and young adults in their 20s who did less paid work. They did care work and learning.
1
42
6
395
25,843
proper use of ai . look at them having fun . so happy picking their apples .. theyre so good at it
Apple harvest with the help of artificial intelligence!
241
8,473
180
98,800
2,195,979
People who died of hunger in 2023. ↳ 8,893,033 Deaths from GMOs in the last 30 years. ↳ zero. 30 years. 70 countries. 4400 risk assessments. All conclude that GM-crops present no greater risk to human health or the environment.
This is the right time for an initiative to scrap the entire, completely outdated EU #GMO directive. Not one of the Frankenstein scenarios of the NGOs has materialized, not a single person on the entire world has developed any GMO-related health problems.
9
178
8
542
22,126
When your feature tree breaks, it’s often due to issues with the naming algorithm. Yet, most CAD designers don’t understand what naming is and how it works. When you create a parametric feature tree, it generates a linear sequence of operations that define the geometry. To change the geometry, you go back to an operation, change a parameter, and “replay” the subsequent operations. However, there is a problem. Every operation takes edges, faces, or bodies as inputs. These geometries are recalculated every time the operations are reevaluated. For a CAD system to consistently identify a geometry, it must define a strategy to assign consistent unique IDs to every single edge, face, and body. This strategy is called the “naming algorithm.” So, how does it work? I often see people think that a CAD system might try to identify geometry based on similarities in size and shape after a feature tree update. For example, when we create a cylinder and apply a fillet on the top edge, after updating the cylinder’s radius and height, the CAD system could try to find a circular edge on the updated cylinder that’s the closest in location and size to the original filleted edge and apply the fillet on that edge. This would be a terrible idea. Why? Because the user’s original intent was to place that fillet on the cylinder’s top edge. If the location of the cylinder changes in a way that the bottom edge moves to where the original top edge was, the fillet will be applied to the bottom edge. That’s definitely not what we wanted. So instead of using geometric similarities to identify elements, CAD systems use the parametric history of the geometry to assign unique IDs to them. The root elements, which are usually 2D sketches, get unique names assigned to them when they are created. By extruding, lofting, sweeping, or revolving a profile, the new geometry will create easily distinguishable elements: 1. A bottom face 2. A top face 3. Side faces The bottom and top faces will get names like “bottom face of the extrusion of rootProfileX,” and the side faces will get names like “side face2 of the extrusion of rootProfileX,” where face2 means that the face was generated from the second edge of the profile. The same logic applies to subsequent operations, except that they might refer to these generated names instead of "rootProfileX." It’s a bit like when royals are referred to with their entire lineage: King Jack, the son of Jane, the daughter of Jim. Now that we have names for all the faces, let’s see how edges are named. In boundary representation, a solid body’s edge is simply the intersection of two faces. Thus, the name of an edge is “shared edge of face1 and face2.” Sounds super simple, right? Haha, nope. Unfortunately, even in simple cases, two faces might have multiple intersections. For example, imagine a cylinder with a cylindrical hole punched through it perpendicularly. The two cylindrical surfaces will have two intersections. So what can a CAD system do in this case? A lot of heuristics. More sophisticated CAD systems will use parameters, relative locations, and other information to assign a unique ID to both edges, but unfortunately, there is no perfect solution. Naming is a major source of broken feature trees. Here are a few examples of what can go wrong with naming: 1. You refer to an offset face in an operation. The offset value changes, and the face splits into two faces. Now we have two faces where we used to have one. Which one should get the original name? 2. You use a filleted edge’s curve to constrain a sketch. The radius of the fillet changes, and the edge disappears. Bam, you have a broken reference. 3. You cut a cylindrical hole into a sphere and apply a fillet on one of the intersections. You move the cylinder a bit, and as you are moving it, the fillet magically appears on the other edge, then jumps back and forth. Unfortunately, the heuristics in this case didn’t work very well. Fortunately, it’s often quite easy to avoid these situations. By understanding how naming works, you can consciously plan your parametric feature tree to create a robust feature tree that rarely breaks.
5
11
3
112
13,825
I disagree that Software Engineers should be accountable. Everyone writes bad code. Some more than others. If that bad code can be easily released to cause havoc in the real world, the problem is the management and processes that enabled it. Hold the company and its management responsible. All programmers that I know wish they could spend more time on tests, have better QA processes, have good practices like canary deployments, etc. We have to actually force ourselves to release code we don't think is good enough because management is standing there tapping their foot and pointing at their watch. The problem at Crowdstrike isn't the engineer that messed up, because all of their engineers will mess up sooner or later. The problem is the poor processes they have in place, a lack of sensible precautions like canary deployments and sufficient automated and manual testing. The fault lies 100% with management, and I hope they are held accountable in the lawsuits that follow. But watch them pay themselves hefty bonuses while they shift the blame to the people at the bottom of the hierarchy who didn't have responsibility or a say in the matter.
382
314
101
2,917
305,927
Mario in the Multiverse - Teaser Trailer
245
4,440
239
22,117
856,553