Reddit reviews Start with Why: How Great Leaders Inspire Everyone to Take Action

This book has been suggested a few times so I finally got around to reading it. I think it has some good information in it. I'm only about halfway through it, but I like it so far.

Time Management for System Administrators

Other books would be any of the social books like "How to influence people", "7 healthy habits..." Etc.

I haven't read this one yet, but It has been suggested to me if you plan to go more into management/leadership Start with Why

Other books that have I have ear marked due to being mentioned:

• The Devops Handbook
  
• The Practice of System and Network Administration
  
• The Practice of Cloud System Administration
  
• Cognitive Behavioral Therapy - This one might have been a joke, but as someone who has dealt with depression and burnout on the job. I think this could be beneficial.
  
• How to win friends and influence people
  
• How to win friends and influence people in the Digital Age
  
  Also, do a search for "Books for IT Professionals" to find a lot of other suggestions.

http://www.amazon.com/How-Win-Friends-Influence-People/dp/0671027034

http://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447

http://www.amazon.com/gp/product/0143124986

When Breath Becomes Air - Paul Kalanithi

Being Mortal - Atul Gawande

Better - Atul Gawande

Honestly anything by Atul Gawande

Start With Why- Simon Sinek (Just finished this one today. Phenomenal read. Not medicine related, but a great perspective on what leadership means and how you can inspire those around you)

The White Coat Investor - James Dahle (Financial literacy is always a good thing)

​

I have quite a bit more book suggestions if you're ever curious, but those should keep you busy for a while. Feel free to DM me if you want more!

Wow...
https://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447
Your fundamental problem is that you need to start with what you are trying to do, then work to get the data in the right shape to meet this need.


GOALS:

Show the availability of resources with a given skillset over time. You want to allow for resources to learn new skills.


DIMENSION TABLES

Now that we know what your goal is, let's look at the actors that you have defined to determine what dimensions you need.


"Show the availability of resources with a given skillset over time" The nouns in your goal will give you the dimensions that you need.


Employee- DIM_EMPLOYEE (don't call people resources... they just don't like it :) )
Skillset- DIM_SKILLSET
Time- DIM_DATE (if you are calculating availability down to the hour, then you will also need a DIM_TIME table)
FACT TABLES
"Show the availability of resources with a given skillset over time. You want to allow for resources to learn new skills." The verbs will give you what needs to go into your fact tables.
These fact tables will be a little tricky depending on how complex you want to make them.

Availability- you are looking to capture the availability of a resource and compare it to the demand for a given skill.

​

​

but... unfortunately, I have to go. I will try to add some more to this later. Hopefully, this is enough to help you a little.

>I feel as though I'm going to be "messing up" alot with clients.

yes. A lot. It's normal

BA in kin would be a waste of time unless you plan on doing physical therapy or want to work in more clinical settings.

I'd suggest reading and messing up with clients; it's the only way you'll learn. Two books that offer fairly different, but great, base beliefs as well as programming are

Starting Strength by Mark Rippetoe

New Functional Training for Sports 2nd Edition by Mike Boyle

as well as Start with Why

Only one title of overlap, nice.
Out of your list, where would you start? Have you read any other in our original list?



Built to Sell, John Warrillow

The Automatic Customer, John Warrillow

How to Sell at Margins Higher Than Your Competitors, Lawrence Steinmetz

Start With Why, Simon Sinek

Leaders Eat Last, Simon Sinek

The E-Myth Revisited, Michael Gerber

Selling the Invisible, Harry Beckwith

What Clients Love, Harry Beckwith

Question Based Selling, Tom Freese

Are your customers loyal clients or just one time clients.

Go read / listen to this book. Talks a bit about it.

https://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447

There are already some great ones posted so I'll just go with a couple more... non traditional ones that are surprisingly helpful.

Purple Cow

Start With Why

I'm reading Elon Musk's biography right now and think it might be helpful if you're talking about career success. The dude seems like a jerk but has an incredible work ethic and drive to succeed.

You can say pretty much the same exact thing about Augustus' biography.

Outliers really helped me a lot, because it made me realize talent wasn't nearly important as skill/effort. You put in the time and effort and you will develop your skills.

If you're an introvert like me these books helped me "fake it till I make it" or just want to be more socially capable: Charisma Myth, anything by Leil Lowndes, Make People Like You in 90 Seconds. Not a book but the Ted Talk about body language by Amy Cuddy

A book on leadership I always hear good things about but haven't read yet is Start With Why.

He also has a book on the subject which might be of help to you: http://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447

I'm reading it at the moment and so far so good, but the bulk of the idea is covered in the Ted talk.

Absolutely! Here's a short list of non-magic books that I commonly see recommended to magicians.

Understanding Comics - Scott McCloud

Purple Cow - Seth Godin

Delft Design Guide - multiple authors

An Acrobat of the Heart - Stephen Wangh (shouts out to u/mustardandpancakes for the recommendation)

In Pursuit of Elegance - Guy Kawasaki

The Backstage Handbook - Paul Carter, illustrated by George Chiang

Verbal Judo - George Thompson and Jerry Jenkins

Be Our Guest - Ted Kinni and The Disney Institute

Start With Why - Simon Sinek

Lots of common themes even on such a short list. What would you add to the list? What would you take away?

Yes.

1. Small Giants
   
   
2. Start with Why
   
   
3. Influence
   
   
   Start with #2.

Hey there!
UX Designer/Researcher here. I came from a background in Psychology and Neuroscience research before UX Design. Personally I used the UCSD Extension for a certificate in UX Design. I really appreciated the course work and in conjunction with the Coursera Interaction Design felt like I was given plenty of exposure while also having flexibility to work.
From my experience in the industry, I would look into what area you are interested in. UX careers can involve programming and development, but I use absolutely no coding at my current position (at others I have though). The biggest selling point to an employer is showing an understanding of the process: wireframes, flow charts, user studies, iteration (agile/scrum/waterfall), and design understanding. I have worked on multiple billion dollar webpages and can say the process is nearly identical when scaled down.
If you are interested in some resources to start on your own I would recommend Simon Sinek's Start with Why for understanding how to look at design solutions.
Don Norman has many great books, including The Design of Everyday Things.
Some actual books to look at and learn on your own are A Project Guide to UX Design, Lean UX, and The UX Book. I highly recommend the last one I find it very thorough and digestible and for ~60 bucks is a reasonable textbook.
Lastly, once you have a grasp of UX as a concept I would get familiar with the Adobe Suite, Axure or InVision, and any others from career sites that you might not know about (I really like [Sketch]() as a cheap option ~$99).

Best of luck, feel free to ping me with questions

Hi! Sorry for the delay, I wanted to answer this correctly (and I'm happy to discuss it further).

> If anyone else than Symfony created a HTTP client, I would argue you wouldn't have answered with the same level of questioning.

Agreed.

> it means Symfony has a reach and people expect high quality packages coming from it.

Yes high quality is a criteria, but it's not the one thing. I think the key here is the impact: Symfony has a lot of weight in the community.

> But it's also a shame, because it tends to demotivate people trying to innovate. When everyone is asking you to justify every single action you do, you tend to stop because you're tired, especially if you do it for free.

Understood, sorry about that. I'll try to be careful about the way I say things.

The thing is that it's hard discussing some topics, and this is something I see often: either you say nothing (and avoid any risk to hurt or displease anyone, or even look like a fool), either you speak, but you need to find the right words and formulate it in a constructive way.

I want to speak about this topic because I care. And because most developers I am discussing with are unhappy as well (but none of them is saying much). I find it disheartening to see this (given how Symfony is important and used, and how many people work on it - including for free as you said), and my goal is to share this in the hopes that things change somehow. I am not looking to dismiss anyone's work.

Now let's try to discuss the actual topic:

I agree that it isn't just about Guzzle vs Symfony's new component, or even PSR-18 (which is why I don't think it's worth discussing specifically about this). A few facts:

• Symfony left the FIG, and before that wasn't really involved anymore for some time
  
• Symfony reimplemented some projects that existed and were used by the community (Guzzle is another example, but another example that comes to mind is DotEnv)
  
• Symfony Flex changes how Composer, the most standard thing in PHP, works
  
• Flex recipes are controlled by Symfony in a repository (whereas Composer is an open thing)
  
• the PHPUnit bridge highjacks PHPUnit's behavior (again, one of the most standard package in PHP)
  
• some new components are discussed "in private" and announced to the community, where it used to be discussed openly before
  
• (I'm stopping here because you get the point)
  
  Now I hope I portrayed these as facts (and I may have some of them wrong). I completely understand that many of these things happened because of good technical reasons.
  
  But if you look at it from what "it looks like": Symfony seems to be aiming to be a closed ecosystem. Symfony used to be the open framework, built upon reusable components and compatible with any PHP library out there. Now it feels like things are changing (note I am talking about a feeling, it may actually not be the case but that's what some people feel). For example some people believe that the next step for Symfony is to reimplement Monolog as a component (and possibly ditch PSR-3), and the next step would be Doctrine. Same goes for API Platform. Personally I think it's possible that this may happen.
  
  And things can change, it's fine, but here it seems like it's a whole change of identity. And I think that's why some people feel uncomfortable, and that's why as well it's so hard to voice (because it's intangible).
  
  Lately I've been reading Start with why and it explains it very well. Nobody complains about Laravel releasing stuff in a closed ecosystem: that's what Laravel is about. It's part of its identity. Symfony's identity has (from my perception) always been different: more open, more about the community, etc. Maybe it's time to redefine clearly the Symfony identify (and explain that it's changing)? Maybe it's just a communication issue? I don't think it's a technical issue in any case.
  
  Anyway as you can see it's not easy putting words on all of this. But to reiterate: I'm talking about how some people feel (to give concrete number it's between 5 to 10 people). And I feel like it's worth talking about it because I care about the Symfony and the PHP community. I hope that helps!

> WHO matters most, then WHY, then HOW, then WHAT, then WHEN. Hire the right people with the right motives who follow a great plan and what you do and when you do it should work out on it’s own. x 2

This is kind of wrong. It should be Why > what > how > the rest.

You first have a purpose. Then you have a product. Then you have how you did it.

You can find more info here: https://www.youtube.com/watch?v=qp0HIF3SfI4

and here: https://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447

Selecting business ventures based off of market — or lack thereof — is not the best motivation.

I would advise you read this book:

http://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/1591846447

Start With Why [Simon Sinek]

48 Laws of Power [Robert Greene] (33 Strategies of War, Art of Seduction)

The 50th Law [Curtis James Jackson]

Tipping Point:How Little Things Can Make a Difference and Outliers: The story of Succes [Malcolm Gladwell]

The Obstacle is the Way, Ego is the Enemy [Ryan Holiday] (stoicism)

[Tim Ferris] (actually haven't read any of his books, but seems to know a way to use social media, podcast, youtube)

Get an understanding to finance, economics, marketing, investing [Graham, Buffet], philosophy [Jordan Peterson]

I like to think us/you/business is about personal development, consciousness, observing recognizable patterns in human behavior and historical significance. It's an understanding of vast areas of subjects that connect and intertwine then returns back to the first book you’ve read (Start with Why) and learn what you've read past to present. Business is spectacular, so is golf.



To Add:

Irrationally Predictable:The Hidden Forces that Shape Our Decisions - [Dan Ariely] (marketing)

The Hard Things About Hard Things - [Ben Horowitz] (business management)

Black Privilege: Opportunity Comes to Those Who Create It - [Charlamagne Tha God] (motivation)

The Lean Startup: Use Continuous Innovation to Create Radically Successful Businesses - [Eric Ries]

Zero to One: Notes on Startups, How to Build the Future - [Peter Theil]

I'll give you two book tips:

1. Never split the difference by Chris Voss, an ex FBI hostage negotiator. This is about negotiation techniques that everybody can use. A better negotiator has more power. Negotiating is not about overpowering and bluff, it's about finding common ground and making a connection.
   
2. Simon Simek - Start with why. This book was for me really useful, but given your situation, your "why" may be very clear. Still it's a good book as your "why", your (underlying) motivation may not be entirely clear to yourself. Sometimes you do things without really knowing why. Don't expect this book to explain the whole complexity of your inner self - it doesn't, but well - if you have the time and energy, it might help.
   
   I don't know if you can order these books. Both are available as EPUB as well if you use a normal e-reader or laptop.