becoming an influencer

put the camera down pick something you want to learn about spend thenext 10 years mastering your craft pick the camera back up tell peoplewhat you have learned kill it

small, sharp tools.

article Rule of modularity:write simple parts connected by clean interfaces. Rule of composition:design programs to be connected to other programs. Rule of Parsimony:write a big program only when it is clear by demonstration that nothingelse will do. Build as simple as possible, but no simple. Do not allowthe composition of these parts to assemble a tightly integrated system.

Working Effectively

article

  • Problem: staying 'in the zone' is just not healthy or effective for aprogrammer! However, long periods of concentration are vital for aprogrammer to better understand their code and succeed. This crazydedication helps develop unhealthy habits and can prevent you fromproperly focusing.
  • Concentration periods are the most important part of programming.Losing concentration means losing all context, and losing all contextmeans that you'll spend lots of time reorienting yourself and enteringa stronger period of focus.
  • It's difficult to adjust, and this leads to substantially decreasedproductivity. To improve:
  1. Embrace interruptions. Learn to accept interruptions and avoidgiving up through them.
  2. Maintain context outside of your head at all times. Alwaysexplicitly comment and track what you're doing, teh decisions you'remaking. etc. Externalizing thoughts can help you clarify them! Everyso often, make sure to record these (the author does this at 30minute intervals).
  3. Ignore tangental issues. Focus on the singular current task anddon't worry about things that could get you sidetracked! Write thosedown with a ticket system that's fast, lightweight and agnostic tothe amount of detail put into these thoughts. The most importantthing to do is to put this idea away until it can be summoned in afuture context.
  4. Always know of the one thing you will do next.
  5. Prioritize negatively :: assume baseline that you will not do any ofthe tasks, then assess the negative outcomes of not doing each one.Perform the task that will have the most negative outcome first.
  6. Recognize the benefits of breaks. Breaks have great benefits,encourage better health, and can offer a new context from which theproblem can be tackled!

50 ideas that changed my life

https://www.perell.com/blog/50-ideas-that-changed-my-life inversion ::avoiding stupidity is easier and better than being brilliant doublespeak:: saying the opposite of what one means theory of constraints :: focuson the bottleneck, the weakest point of the system, always. preferencefalsification :: lying to conform to the most socially acceptableopinion at the time mimetic teory of desire: rather than having our owndesires, we imitate the desires of others and pursue their ideas mimetictheory of conflict :: similar = fight left off on 10! on automating outof work The best work isdone when you do it for yourself. you sign your brains away when you goto work for a big company, and these people will likely be B players –no matter how many great people they hire. most A players have moreimportant things to do with their own time. without ownership, there isa high chance that you will not be at your best. non-technical business:: sometimes daily tasks do not end up driving revenue! the others aredriving the revenue, you are maintaining thigns for them. their capacityto define tasks for you may not ever outpace your ability to deliver.automating yourself out of a job could be a goal, but this doesn't work:

  • system complexity means something can always break!
  • markets rapidly evolve and parts cease to work in the future!

is self-automationethical?

  • automation and the 15 hour work week from keynes
  • though automation continues, humans find ourselves working longer andlonger hours – even though we enjoy benefits from those who useautomation and those who owned automated products.
  • Automation still has the power to reduce the amount of boring work wedo.
Revisions
DateHash
2023-02-22
Navigation
Previousweb_design
Nextmessaging
Uppages