Denmark... Is A Elitist, Right Wing Country

Denmark... is a elitist, right wing country

( Trigger warning, if you do not wish to hear about my political posts, blacklists the tag Danish Politics") So I am a Dane. And weirdly enough for my atheist, polyamorous self, I actually do want to be proud of my nation. And I AM, of several things Denmark have done... But overall? No. Denmark have widespread corruption ( A test in the spring of 2023 of "Who is willing to take bribes if we offer them 50k DKK (About 7.5k USD)" had 91% of politicians in parliament saying yes please) but a lot of the success of Denmark is based on what people THINK of Denmark, rather than what it actually is. For example, I finished university currently. And not only did the Uni teach students a way of doing databases that was in direct breach of GDPR (I documented this, and still have it all, since at the end of my education, I did not trust the university at all), but in at least 4 classes, the teacher did not bother to define what the students had to do to pass. In my robotics class, our final papers definition was "It must be 5 pages". That was it. No topic, no focus, no anything. You could still fail, but the requirements was inside a professors head, and you had to guess. If you ask the universities they will tell you that they received basically no complains. They forget to mention that there is no way TO complain. Despite this completely incompetent behavior, people having a danish education is thought of as high level. Because we used to be. Basically anything good you hear of Denmark, is inertia from its behavior in the 1990s (30+ years ago). Today it is a corrupt, right wing extremist state like so many other disappointments. We still have rights, but they are getting removed. And the majority of Danes do not care. They are busy yelling their sympathies to Israel.

Guild Structure

Wanted to write a long reply to this post:

Spreading experience around is always awesome! :D

It is good for the firm you are working at as workers perform better.

it is good for whoever is getting taught since they get smarter.

And it is good for the one teaching, both for the pleasure but also because you learn a LOT by being forced to explain what you know to someone else. It crystalizes the knowledge and experience you have acquired, and forces you to go through the basics again, but this time with all your knowledge and experience, you often learn deeper, more complex truths, methods and skills from doing so than it is POSSIBLE to do when you learn them while having little clue what they are ( Function pointers and their safer class versions is a classic for OOP programmers ).

There is a structure a firm can use as soon as it starts having separated departments. Departments, while necessary, makes a firm more segregated, and makes it harder for knowledge to flow around.

It is called Guild Structure Or rather... some important context if you google this: "Guild Structure" is the only way I have heard of it, but "Guild Structure" is also a product from a firm called FourWeekMBA... which is a consulting firm that sells services that firms that is... basically helping them implement these ideas... So you can easily risk finding overcomplicated explanations for what it is, since if they made it easy to understand... then they do not have a product...

And it is super simple. Normal development work for engineers and software is done in smaller teams... usually 4-8 people. sometimes all are in a domain (like software, electronics, finance, marketing, etc), and sometimes mixed. Often... either being mixed, or having several teams with different domains meet relatively often, like several times a month is a good idea. Because it stops misunderstandings from developing, since they are caught early. It is a waste when the software department develops functionality that it turns out no one actually wanted (Which happens... a lot more than anyone likes)

Firms, managers and workers are often afraid to do this. Usually for 2 reasons. One bad, and one that Guild structure fixes. The bad one is not wanting to risk looking stupid in front of other people. When software, marketing and finance people talk about what to develop... each domain is asking questions in a domain they are not experts in. That is the symptom and consequences of toxic firm culture. Talk about it in the open, communication is how you slowly work on and attack this, both in firms and personal relationships. Because they are both about making humans work better together.

The other is a fair enough one. Software people will learn a lot of software tricks that are only helpful to other software people. And if software people are spread around in these teams the knowledge cannot flow very well. Basically, while mixing domains fixed a whole bunch of knowledge flowing issues... it created a new one for domain specific knowledge...

This is where you make guilds. Make public guilds. There are clear lists of the guilds, explanations of their domains and several example for each guild for what kind of domain they are covering.

In some firms, a software guild is enough. In others, embedded software, high level software, front end and back end are different guilds. It depends a lot on the firm.

The guilds have communication between all members ( chatrooms usually ) and meetings every month. They will try to encourage knowledge sharing by giving tools, like shared drives where good guides, tutorials and tricks are shared. Sometimes written by guild members, sometimes found online (If you just had the though "Wait... is that not what Codeblr does?" you have just realized that Codeblr is a naturally formed guild), having people who have good ideas they want to spread give presentations during the monthly meeting, rewarding the best idea of the month. People can participate as individuals, or small groups (Tricks are often found by 2-3 people working together).

Meetings can be physical, or remote, or switch between them, doing both.

This basically solves the issue of knowledge sharing. It also empowers workers while making the firm better. Everyone wins!

OMG I LOVE IT!

What is the dumbest thing you have coded and gotten to work?

a discord bot in my friend group server where it would scold people if they swore XD

An example hehe

Oh absolutely. I have written every single report and paper that non-programmers ( Users, pruduct owner, whatever ) in LaTeX.

It is Word. But you can do ANYTHING you want, work in the same updated file if you use overleaf ( Like google docs.... But you know... good... ).

And if you just want to write a basic report with a few diagrams. LaTeX just makes it nice and easy and looks good, dry and professional.

But markdown... Oh markdown is for documentation. And it is perfect.

It is super super easy to use. The "Cost" of this, is that you only have few features...

And that is KEY. Combined with you being able to put pictures in what is otherwise basically cleartext, means that you MUST be able to clearly explain whatever it is you are documenting with nearly no fancy text, colors, weird structureing with the words or whatever.

No. You MUST do it in text... Or use a diagram.

It forces you to use DIAGRAMS in your documentation. Glorious easy-to-read better than a thousand words diagrams.

It removes the horrible middle-ground and lets you focus on making documentation super super fast, with text and diagrams.

Fun fact. Markdown... is a markup language

If you do not know what markup is... you should look it up. It is basically HTML that works both encoded and as clear text. Meaning it is the perfect note taking "language". In reality it is "just" "a convention for how to write super nice-looking notes that have been tested by millions of people to be the very best it can be. No big deal. Oh also it is free, you do not even need a special program to look at it. Your browser can do it perfectly.

You made me wake my dog up from laughter! :D

programmers will complain about how C++ is too complicated or arcane or whatever and then will literally go and write in JavaScript

My husband loves me a lot... despite the task I make that :p

Me, in a jolly mood, once again forgetting to do volume control: "GOOD MORNING HUNEY!" Husband ( In the most loving but tired voice ): " Stop screaming in my ear... you... colossal... moron."

Like... You know how sometimes when you hear people speak you can HEAR the punctuation mark at the end of that sentence. It was NOT a exclamation mark or no punctuation whatsoever.

It was not "moron!" or "moron" It was "moron."