The real deal y0

  • 1 Post
  • 203 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle









  • What im about to say applies to belgium, and i dont know about other countries or companies or how it works if a company from another country has a base in belgium, so take everything i say with a pinch of salt.
    SO
    In belgium every company with more than x amount of employees ( i think its either 50 or 100 ) must have a worker council meeting every month and have worker council member votings every few years, to select what employee will join said meetings with a select few people of the heads of the company. The members are people who have joined a union ( which is just being registered, has nothing to do with your job and which union depends on the job and your political views. Each union is large enough to cause mayhem and force talks ) and have put themselves forward to be in those meetings.
    After said voting, the representatives are selected and join the meetings.
    While the representative is selected him or her can not be easily fired or laid off. While they are registered at a union they also can not be fired without a valid reason, as that would get the company investigated.

    So overall here what union doesnt mean that much, but the process is more important.

    I would also like to point out that i love this whole thing, even if ive worked with a complete asshat that was the workers representative and seriously needed to be fired because he did his actual job (handyman) terribly. The fact he was in those meetings meant the workers were represented and im sure he did that part right as he kept being voted for.




  • Im currently trying to steer a product team to have this kind of process. They are working with an ancient piece of software that is slowly being replaced. However, we need to replace piece by piece while the main app is still being maintained because of law and workflow changes. This is why i want them to set the requirements and designs up front a bit so we can make a good analysis of it before development starts so no technical difficulties or questions arise mid development! However, nothing is set in stone and after each small piece ( aka after each sprint ) we have our review and product owners and stakeholders see what we have made and can chime in, causing us sometimes to pivot what we were making.
    Best of both worlds!


  • Agile has its uses, but like everything you need a bit of both. You need a bit of both waterfall and agile.
    Example : you need to have your requirements before development, yes. But how far do you go in your requirements? If i were to make all the requirements for my current project ill still be busy in 3 years and will have to redo bits due to law and workflows changing. however , we need requirements to start development. We need to know what we need to make and what general direction it will be heading to a make correct software/code design.

    Agile also teaches you about feedback loops, which even with waterfall, you need to have to know that what youre developing is still up to spec with what the product owner is expecting. So even with waterfall, deliver features in parts or sit together at least once every x weeks to see if youre still good with the code/look/design.

    Pure agile is bullshit, but so is pure waterfall. Anything that isnt a mix is bullshit and in the end, it all depends on the project, the team and the time/money constraints.



  • Thats interresting, thanks! Stuff for me to look into!
    I also think halfway through the conversation i might have given the impression i was talking about pointers, while it was not my intention to do so. That said, the readonly/mutable reference thing is very interresting!
    Ill look into what rust does/has that is like the following psuedocode :

    DataBaseUser variable1 = GetDataBaseUser(20);
    userService.Users.Add(variable1);
    variable1 = null; // or free?
    [end of function scope here, reference to heap now in list ]





  • Thanks for the response. Ive heard of rust’s compiler being very smart and checking a ton of stuff. Its good thing it does, but i feel like there are things that can cause this issues rust cant catch. Cant put my finger on it.
    What would rust do if you have a class A create something on the heap, and it passes this variable ( by ref ? ) to class B, which saves the value into a private variable in class B. Class A gets out of scope, and would be cleaned up. What it put on the heap would be cleaned up, but class B still has a reference(?) to the value on the heap, no? How would rust handle such a case?