1,697 karma · joined April 23, 2012
Please... massive redistribution of wealth to the already wealthy strangles both potential entrepreneurship and the customer base it would have attracted since they don't have disposable income. Let's not play stupid here.
Still hasn't happened.
Source on that please? I'm highly dubious.
I understand this is not a popular opinion on news forums anywhere nor do I write this to absolve in my view Tesla of their poor response nor of their poor choice in naming the system 'autopilot' to start.
But at what point does corporate or government responsibility end and personal responsibility start? If I knew something didn't work and that something could kill me and had reported the issue 7 to 10 times, I would be watching, like a hawk for the issue to recur, or more likely just not using it at all.
People have this insane idea that just because something isn't their fault they don't have to take corrective action in order to avoid the consequences. It is better to be alive than to be correct.
When I was consulting I had a build pipeline to production up as my #1 task. Doing this kept me honest and prevented a month of "go to production" issues at the tail end of the project from surfacing but far more importantly was building trust with my clients. They could see what was happening all the time and if something was going off track we could correct it quickly.
Absolutely maddening.
Just don't eat processed food. Also restaurant food uses a ton of salt so tread carefully.
I haven't read the source texts yet (Twilight of the Idols e.g.) but my understanding is that his main goal was to ask people to not-systematize and live the lives of others or wholly subscribe to someone else's philosophy but to live life as a self-creative act in which we are the authors of what gives our lives meaning and purpose. I don't see anything offensive about that.
But I think it is equally short sited to blame the tool.
Whatever tool you choose, you have to FULLY adopt. Everyone has to be bought in, learning the features (like do not disturb), setting ground rules which make sense for your company and how people within it like to get things done.
Seriously, I never felt more productive than when I used Trac, I don't think issue tracking has really evolved much more than that save useful social features and code review (essentially what killed Trac because the Git integration was never very good).
When I look back as to why that was, I realize it was because the WHOLE COMPANY was bought in. We all used it, we all used it well and respectfully.
This is the madness of the agile world. Viewing the tool as the solution rather than just that, an implement, a ways to a means that starts before its usage and and ends after its usage.
> Remote work culture is a defense mechanism against the distracting open office
Disagree as to the reason remote work has become a thing, but I do think it's largely because video conferencing works better every year, tools like Slack exist, and code review tools can be done line-for-line remotely.
But, has anyone seen the Slack diagram for whether or not to send a message? It is extremely well thought out, but settings can't be useful if you don't set them.
> Chat, at least on slack, isn’t grouped or threaded.
Yes they are, now.
> ...non-trivial to know what the current topics of conversation are in a slack channel or to assign one of those topics to any given message.
Then speak up and tell people to stick to the topic, change it, or open a new room.
> ctrl-f, the one constant of web interaction, is broken in channels if you’re searching more than one page up.
Use the Slack client
> Middle managers will make deliverables....
And here is where I stop reading. This is an organizational problem you see manifesting on the tool and you are incorrectly assigning blame to the tool.
--
You have to be committed to using whatever tool is chosen. Just choose one and actually use it.
These tools are a discipline not a freedom from discipline.
I can not highly recommend enough "The Meaning of Life : Perspectives from the World's Great Intellectual Traditions". It's one of The Great Courses and I found, extremely easy to listen to. The topics covered range from the Bhagavad Gita, to the Book of Job, to Stoicism, to Daoism, Confucianism, Bhuddism, and all the way into modernity (Hume, Mills, Kant, Tolstoy) and post-modernity (Nietzsche).
A pervasive theme of ALL cultures with a philosophical tradition is the necessity of living one's life with the moment to moment realization of one's death.
> in the process, we often lose sight of the business problems being solved
And then goes on tangents as to why that is happening finally arriving on what tantamounts to "developers don't like to use visual UI tools".
The original cause identified is right, people lose sight of business goals, but why? Because they have poor project management and they are in the trenches all day long. They want to do right by the code base, so they abstract things which don't need to be abstracted. The failure here is one of trade off analysis and again losing sight of what is important, shipping a usable product which meets business goals.
The author said "prioritize" not to sacrifice profitability in order to learn. By prioritizing learning you may very well increase profitability over the long term. See the recent Google Maps is a moat post.