• 1 Post
  • 286 Comments
Joined 1 year ago
cake
Cake day: April 19th, 2023

help-circle
  • I can’t get what it describes through all the Jedi stuff and jokes.

    One mentor and one apprentice? And everything else remains unspecified and open?

    For FOSS, as it is described, it makes me think it’s a big investment with unclear risk (will they even stay as a contributor?). Which of course can be contextualized - but then what is left here?


  • I sometimes do things (cleanup, refacs) off-ticket / not part of the ticket. It can be a light alternative when other stuff is complicated and demotivating. Depending on your environment and team/contract setup, simply doing it could be more difficult though.

    If it serves your satisfaction and productivity, and is good for the product, then it’s not wasted. Not everything has to be - or even can be - preplanned.



  • I don’t have experience with that in particular. I’ll share my more general, tangential thoughts.

    MVP is minimal. Extending the scope like that makes me very skeptical (towards scoping and the processes).

    Everything you are concerned with would be important topics for retrospectives, or even meetings with management. But of course those don’t exist or are open in all environments. In my team I could openly raise such concerns.

    If you’re always rushing to a deadline, or feel like that, think of what you can do and influence to improve that. Retrospectives? Team disuscussions? Partly tuning out of management given focus and doing what you deem important and right? Look for a different team or employer?




  • The title question is very broad, varied, and difficult. It depends.

    For anything that is not a small script or small, obvious and obviously scoped takes, you can’t assess at first glance.

    So for a project/task/extension like you wrote it’s a matter of:

    Is there docs or guide specifically for what I want to do/add? If yes, the expectation is it is viable and reasonably doable with low risk.

    If there is no guide the assessment is already an exploration and analysis. How is the project structured, is there docs for it or my concerns, where do I expect it as to go and what does it have to touch, what’s the risks of issues and unknown difficulties and efforts. The next step would already be prototyping, and then implementing. Both of which can be started with a “let’s see” and timebox approach where you remain mindful of when known or invested effort or risk increases and you can stop or rethink.








  • …in a very localized and narrow market.

    It’s not that simple of an answer. If you want to label the past working fine as such you also have to accept and include the living standards and social-economic environment. Because our environment and world and how we live today are vastly different from back then.

    How would you barter-trade production parts of a car, the building of a car, and then that car? How would you barter-trade research and technology development?

    Without money, do you pay in a narrow, restrictive way like a place to live and food? Or do you pay in something that can be traded like money - where you practically replaced currency money with a different form of currency money?



  • You copied that function without understanding why it does what it does, and as a result your code IS GARBAGE.

    AGAIN.

    […]

    Debate continued for some time, in a cooler tone, with Torvalds offering suggestions on what he felt would be a better approach to the issues Rostedt hoped to address.

    Harsh tone (in only two instances?), but he still invested in offering suggestions 🤷

    I expected more behind the verb “flaming”.