Live data from Hacker News

It’s time to embrace slow productivity (2022)

newyorker.com

111–120 of 202 posts

Re: It’s time to embrace slow productivity (2022)

#111

Earlier quoted context omitted.

> whoever owns the means of production This 19th rhetoric century doesn't work in modern world, especially when you're talking about creating software. To "produce" most of what HN readers do, you don't need anything more than a laptop and some cloud services — which you would need to scale up proportionally to load, and, therefore, revenue. If you need capital to hire others, it's also never have been more easily av…

You are proving my point. Advances in productivity have led to a lowering to the barrier of entry. Anyone can code now. So why,(in theory) would a business owner let their workers work less when someone else is willing to work longer hours?

If somebody else is willing to do the same job for less, it means your asking price for your services is too high. Americans love to complain about stagnation of wages, while in reality it just means that people in other parts of the world have reason out of poverty competing with them on a labour market. If you value a Chinese life just as much as an American one, the fact that American worker can now afford one car per family instead of two but a Chinese worker can now eat meat on a regular basis clearly is a benefit to humanity.

Re: It’s time to embrace slow productivity (2022)

#112
post #57

I like the saying “slow is smooth and smooth is fast” as applied to software development. For all the talk of Agile processes and breaking creative work down into bite-sized chunks and prioritising collaboration and team productivity over individual contributions, ultimately our work is about thinking and fundamentally it requires that each individual doing the work understands what needs to be done. Not investing en…

Sometimes software engineers forget coding should be the final step, and not the main step. Defining as much as you can,80/20 before starting will save you time. Certainly there are cases where you have an idea and you dive right in and it will work out but usually that won’t work out well from my experience

On this theme I can heartily recommend SovietWomble’s essay on the game the Forest (Soviet was a QA specialist in a former capacity)

https://www.youtube.com/watch?v=PUWg905fGTA

Both funny and insightful for anyone starting a project.

Re: It’s time to embrace slow productivity (2022)

#113

I like the saying “slow is smooth and smooth is fast” as applied to software development. For all the talk of Agile processes and breaking creative work down into bite-sized chunks and prioritising collaboration and team productivity over individual contributions, ultimately our work is about thinking and fundamentally it requires that each individual doing the work understands what needs to be done. Not investing en…

> slow is smooth and smooth is fast Another phrase with similar meaning (and interesting history) is "festina lente" ("make haste slowly," in Latin). I named my company after it (: It's certainly an ancient concept. I feel like software is ultimately about humans organizing complex activities, and humans haven't changed that much in the past few millennia, even if the activities have gotten more complex and abstract.…

Another saying "work smart not hard", i.e. you can save a lot of time by thinking things through before jumping into executing.

Re: It’s time to embrace slow productivity (2022)

#114
post #40

Comments here so far seem to be missing Newport's key point (in the second half of the article)... For many modern (knowledge work) jobs, it's volume of tasks, not duration, that seems to induce burnout. For instance, if you have 1 central task for the week--say, write a report--but there are ten subtasks (hold 5 meetings to prepare, read 3 background papers, ...), and then each of those have a bunch of subtasks (Sla…

It's both. Burnout is when you invest too much emotionally in something or someone and don't get anything back from it. That can be because you have a steady stream of work items and none seem particularly important but you feel obligated to do each one. Or it can be because you labor on the same project for years and never complete it. Or it can be because you work hard and deliver but events outside your control ma…

On behalf of your team, thank you for taking good care of them.

As someone who has been in a team situation without a good manager (where every little thing got highest priority) and subsequently got burned out (also my fault to get too emotionally invested in the work) along with most of the team, I know firsthand the damage that bad management can have on morale, throughput and quality.

Re: It’s time to embrace slow productivity (2022)

#115

More importantly, I think, with AI automation coming in full force, we need to decouple one's working hours with their right to live a comfortable life, especially for the lower and middle class.

The LLMs driving the current AI hype aren’t very suitable for implementing automations, so I don’t see how that would come in “full force”.

Re: It’s time to embrace slow productivity (2022)

#116

I would encourage a focus on "right productivity," (doing the right things at the right time with the right pace, rather than merely doing more or less.). The key to "right productivity" is finding the right balance between quality and quantity, speed and deliberation, work and rest

That doesn’t say anything, because any mode of operation can fit that description, with a suitable definition of “right”.

Re: It’s time to embrace slow productivity (2022)

#117

I like the saying “slow is smooth and smooth is fast” as applied to software development. For all the talk of Agile processes and breaking creative work down into bite-sized chunks and prioritising collaboration and team productivity over individual contributions, ultimately our work is about thinking and fundamentally it requires that each individual doing the work understands what needs to be done. Not investing en…

> slow is smooth and smooth is fast

I've been in enjoying the converse of this i.e. "fast is smooth". It was provoked by using an ultra-fine fountain pen nib - too slow and it would be scratchy and dig into the paper with poor ink flow but using it very fast and lightly and it would be really smooth and delightful.

I am prone to perfectionism, overthinking, procrastination, majoring in the minors and getting derailed by little hiccups. I get motivation by seeing progress. If I pause I can struggle to get started again so momentum is really important or I fall into a negative spiral.

For my personal productivity, it helps to force a pace and do things faster than I naturally want. I need to keep up momentum and quickly do the known things and discover the problems early that need time to percolate in the back of my mind to reach a creative solution.

I guess we all need productivity epithets that counter our dysfunctional traits - too slow then speed up! too fast then slow down!

Re: It’s time to embrace slow productivity (2022)

#118

Earlier quoted context omitted.

Isn't changing requirements one of the key principles of the Agile manifesto? If so, why do we want to dive so much into requirements that are likely to change anyways? Not saying we should jump into design without understanding the requirements, but sometimes requirements are incomplete or not clearly defined and we cannot sit and wait until a new revision is out or someone becomes available to answer our questions.…

Isn't changing requirements one of the key principles of the Agile manifesto? If so, why do we want to dive so much into requirements that are likely to change anyways? Who says all the requirements are likely to change anyway? That’s a whopping great hypothetical on which the entire premise rests, but YAGNI applies to development processes as much as to code! Yes, requirements often evolve and we often start with so…

The tricky bit, in my experience, is that when you straight up ask the customer for requirements you get a list full of details around specific functionality -- basically all the stuff that's going to change in a month.

It takes skill and effort to abstract from these detailed wishlists into generalised primitives which remain somewhat constant. This work is similar to the fuzzy logic social scientists work with, and that's exactly the sort of thing most techies are not very good at.

Re: It’s time to embrace slow productivity (2022)

#119

I like the saying “slow is smooth and smooth is fast” as applied to software development. For all the talk of Agile processes and breaking creative work down into bite-sized chunks and prioritising collaboration and team productivity over individual contributions, ultimately our work is about thinking and fundamentally it requires that each individual doing the work understands what needs to be done. Not investing en…

[deleted]

Re: It’s time to embrace slow productivity (2022)

#120
post #62

Earlier quoted context omitted.

Work is where you provide value to the society, create something for other people and make world better, while simultaneously applying and improving your main set of skills. Why wouldn't you want tie your identity to something like that? Just to be clear: I have a few hobbies aside from work — I make music, DJ, paint, cook, hike sometimes. I have friends, and I'm also not a productivity maniac (I actually work in a 4…

> Why wouldn't you want tie your identity to something like that? Because conflating _need for purpose_ and _need to pay rent_ can be tricky business: they don’t always join neatly. Happy they do for you!

Need to pay for rent is quite literally need to pay back to other human beings for shelter, one of the most basic human needs. Why would it be a bad purpose in life?
Post reply on HN