AggressivelyPassive

  • 12 Posts
  • 358 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • That is absolute nonsense. SUSE mostly serves large enterprise customers.

    And where do you think the people deciding what to buy get their information? Mind share is important.

    I’m pretty sure SUSE is bigger than Canonical.

    That’s actually surprising to me, but I’d argue that Suse offers more products, it seems like Rancher, Longhorn, etc. have no canonical equivalent.



  • And you really think, people who are willing and able to buy enterprise support for their Linux distro get confused by the naming? Sure, there’s that one confused dude, but you also have people asking Facebook where they left their keys.

    OpenSuse is essentially free marketing for SUSE, nobody would know them otherwise. Why would you give that away?

    Suse is not a huge company, it has neither a large enterprise backer nor any killer features, and its market share is relatively small compared to Red Hat or Canonical. Throwing away free marketing while alienating a relatively passionate community is a kind of brainrot only MBA can come up with.







  • None of the things you mentioned were in my description. You made that up completely. I talked about meetings, no scheduling information.

    She’s not entitled to asking multiple times day if you’re done yet.

    Did I even imply that? No. You made that up.

    I work above senior, have done management and tech lead.

    Hearing only what you want, not what the other person said makes you almost perfect management material.

    Seriously, look at my comments and your replies. You answered to a completely different reality.


  • Nah, I think you’re mixing things up here.

    “Toxic” is just a label you’re putting on everything you don’t like and you’re also putting a ton of implications behind it.

    If Stacy wants a feature, and she’s the official representative, I need to clarify what that feature means. A manager can’t shield me from having to research the technical implications, that’s my job.

    Also, you can ignore calls all you want, if there is a genuine need to communicate, you need to have that call at some point. That’s actually your first point in the list above.

    I think you never worked in a role above code grunt. As a senior developer, my job is to do all what I described above. I need to do all the technical legwork a manager can’t. I need to write everything down. I need to get feedback from stakeholders. That’s nothing a manager can do and that’s nothing a junior can do.

    I code something like half an hour a day.


  • I feel like these memes of hating everything other than lone coding is because you keep working for toxic companies.

    No, it’s because we are working with humans and their deeply flawed organizations. As much as people hate corporations and love startups, both are always a mess. Every organization I’ve seen from the inside is barely functioning. Cruft, interpersonal conflicts, incompetence, or simply very bad market situations.

    Software engineering kind of has to get involved with almost all of that. If you need to get approval from department A and Stacy just keeps changing what she wants, you’ll have to carry that chaos into the development and it will usually percolate through half the engineering department, because hardly any interface is actually a stable attack surface. That means meetings, calls, meetings, reviews, meetings, and fucking Stephen again wants to pitch this weird framework he’s so in love with, meetings, budget calls, because there’s no way, simply changing the field length can take that much work, meetings, …




  • I mean this subtitle right here gave me a pretty good idea what’s this initiative is all about already, but that’s just me I guess

    But what does that mean exactly? Fairphones with long support duration? Solar powered software developers?

    I get a rough direction from that, but nothing else, but it’s a headline, that’s ok.

    What really bugs me is that the body of the text doesn’t really explain it either, but needs hundreds of words for that. It’s just fluff for a press statement that should have fit into a tweet.

    Also, keep in mind that people from different countries work on KDE, and English is not their first language, I don’t know what are your expectations… on how the writing should be…

    Well, given that I’m from Germany and English is not my first language, and also given that I’m neither very good at it nor do I have a PR team, I would expect writing at least on my level, I guess?

    But here’s the thing, take a look at Google or MS posts about sustainably and being green, and you’ll realize, truly realize how one could say so much without saying anything… this wall of text that you’re talking about is full of insights

    And these companies are the benchmark? I mean, can’t we expect more from a nonprofit? There are some insights, yes, but they’re drowning in the wall of text.

    Just as an insight for you: a news article is supposed to increase in detail level from top to bottom. The headline shows the rough topic, subtitle slightly expands on that, the first paragraphs tell the actual story, the next paragraphs provide more and more context. The idea is, that a reader can stop reading if she feels like there’s been enough context.

    Look at the article here and ask yourself if it fits this description.


  • Why would I not say that?

    Clearly they can’t get their point across. And I don’t know, why people down vote me for that.

    KDE starts a new initiative, and does so by creating a giant wall of text that says very little about the initiative itself. So little in fact, that people here obviously don’t understand what they’re actually trying to do. That is bad communication. Simple as that. And given that this is not a random blog post, but a press statement, I’m pretty sure a bunch of people read it before publishing it.