Best industrial management & leadership books according to redditors
We found 17 Reddit comments discussing the best industrial management & leadership books. We ranked the 14 resulting products by number of redditors who mentioned them. Here are the top 20.
The future direction of news and how it can be improved
Links in this section are RSS feeds
Jay Rosen is my favorite author on the subject:
Jeff Jarvis is nothing to shake a stick at either:
And finally, we can't forget Clay Shirky:
Presentation design and using visuals to increase group effectiveness.
Links in this section are to books
EDIT: formatting
Kaizen is a cycle of continuous improvement. <act> <plan> <check> <do>.
it's a bit simplified when you put it like that, because it oversimplifies some process that ought to be given full attention (goal setting, plan making as examples, and sometimes it's not as simple just to <do> a 'thing'.) but... but there you go.
For a quick little overview, i suggest this pocket-book... super quick read. it's a bit business oriented rather than self improvement, but it's pretty casually written regardless, so you should be able to apply it to whatever you want in your own life.
so, to answer your questions - i generally start with the goal-setting part, develop a loose plan, and then act on it.
goal setting can be easy, especially if you keep it simple, but if you want to go big life-goal stuff, start looking 'how to make a 3-5 year life plan'). you can follow the internet advice, but i suggest embellishing their basic structure a bit for personalization and function. Also look up s.m.a.r.t. goal setting to give yourself an extra set of guidelines.
then planning... that's pretty goal-specific. just start with big picture stuff, sometimes it helps to put it (action points/tasks/activities on a timeline.
Then the doing... I'm a big fan of /r/thexeffect. I highly suggest taking a look thru there and see what they do. very useful tool.
Something awesome and hardcore like Principles of Lean Product Development ? :) http://www.amazon.com/The-Principles-Product-Development-Flow/dp/1935401009
I agree that doing things one step at a time is important.
There's a brilliant book on managing new product development called Principles of Product Development Flow, and one of the principles (and the one with the most memorable name) is called the Batch Size Death Spiral Principle. The idea is that if people think they will have to wait ages to get their feature out, they'll try and tack it on to something else going out. This causes further delay to the original release, so more people try to squeeze changes in. Everything, the batch of changes is so large that everything is paralysed.
To me, this is one reason to replace Core with Classic. Core have shown themselves to sabotage any change against their own interests, and the expectation is that even if Core propose a 2MB increase, they'll likely block any other hardforks in future. With Classic we can reasonable expect that we'll be able to have sensible discussions about future changes, and the risk of doing several major changes one after another is much lower than trying to do them at the same time.
This is a very good starting point. Our "bible". If you have any questions or have serious interest please PM me. I love talking about this stuff. Seriously, I'll take questions about specific problems.
I'd say that the answer to your question depends on the problem. For certain problems, such as detecting faces, there are functions out there that do everything for you. For other problems, such as circle detection, combinations of existing functions will get the job done (as MakingMacaroni describes in another comment). Then for some problems, such as abandoned luggage detection in airports, you really do need to be up on the current research and have a solid grasp of the mathematics involved.
I'd say that the task you're describing is probably in the second or third category. You might try thresholding optical flow over time, as RGKaizen suggests. Depending on how much training data you have to work with, you might also try training a machine learning classifier on one or more visual features to generate profiles of "normal" and "emergency" situations. If you expect big green tanks to appear or fires to break out, blob detection with color histogram analysis might even do the trick. They key is to make the problem as easy for the computer as possible, and figure out which of the functions OpenCV gives you are best suited for your particular situation.
Best of luck! If you go forward on this project, please let us know what you come up with!
EDIT: Here are a few resources for figuring out which functions to use, what math to apply, etc.:
Many computer scientists (and software engineers) use the scientific method. This book is a good starting point.
Here's a book on the concept Jugaad to Systematic innovation written by an IIMB prof who teaches strategy. Not a bad read on India's tech innovation, though a bit academish and dry.
i have these books currently.
only one is a novel.
&nbsp;
the last 3 are quite new. can lend one at a time.
the first 3 are quite old. not torn.
pls return after reading. :)
like any ?
The electrical relay company I work for super into World Class Manufacturing right now
https://www.amazon.com/World-Class-Manufacturing-Richard-Schonberger/dp/1416592547
> Of course that's what labor does, generically speaking.
That's exactly the point...
> But labor isn't the only way to add value.
Again, for the 88th time in this goddamn thread, I never said it was...
> But you kinda implied that the only way to add value was with labor.
Provided we can answer the damn question, then we can go to the next point. And that's whether or not active labor should be a Capital requirement for everybody.
> Catchy platitude. Like most catchy platitudes, not that meaningful when you think about it though.
You know the difference between LMF and KMF? I'm guessing not...
> Why should "capital" serve labor?
Because human need is more importance than servicing the wealth creation of Capitalists.
I'd like to believe that this isn't rocket science. The cost of materials should be straight forward to calculate. The time to assemble and weld is as much experience as it is a documented craft.
Not to be an jerk but this book: https://www.amazon.com/Estimating-Costing-Manufacturing-Industries-Engineering/dp/0824787129, came up on my very first search of the net. This was the second: https://www.amazon.com/Commercial-Steel-Estimating-Comprehensive-Mastering/dp/0831134399. I'd buy the books and save yourself some stress taking college courses.
I'd add the following two books to the list to cover TDD and the Software Design phase:
Disclaimer: I haven't read the latter but am familiar with the contents from courses I've attended with Mr. Gilb. Won't help you how to code but what to code when doing it on a contract.
good to great is known to be a joke of a book. You cannot take any of their findings as fact due to the highly unscientific methods they undertook. The book is highly prone to the halo bias.
You appear to be out of the loop. Or maybe you were born between 1978 and 1991 so you don't realize there's anything unusual about you: http://www.amazon.com/Not-Everyone-Gets-Trophy-Generation/dp/0470256265