best-practice   1804

« earlier    

YC’s Essential Startup Advice
The Pocket Guide of Essential YC Advice

• Launch now
• Build something people want
• Do things that don’t scale
• Find the 90 / 10 solution
• Find 10-100 customers who love your product
• All startups are badly broken at some point
• Write code – talk to users
• “It’s not your money”
• Growth is the result of a great product not the precursor
• Don’t scale your team/product until you have built something people want
• Valuation is not equal to success or even probability of success
• Avoid long negotiated deals with big customers if you can
• Avoid big company corporate development queries – they will only waste time
• Avoid conferences unless they are the best way to get customers
• Pre-product market fit – do things that don’t scale: remain small/nimble
• Startups can only solve one problem well at any given time
• Founder relationships matter more than you think
• Sometimes you need to fire your customers (they might be killing you)
• Ignore your competitors, you will more likely die of suicide than murder
• Most companies don’t die because they run out of money
• Be nice! Or at least don’t be a jerk
• Get sleep and exercise – take care of yourself
startup  best-practice 
18 days ago by stephan.poetschner
Small Functions considered Harmful – Cindy Sridharan – Medium
I’ve worked on codebases inherited from folks who’d internalized this idea to such an unholy extent that the end result was pretty hellish and entirely antithetical to all the good intentions the road to it was paved with.
The best abstraction is an abstraction that optimizes for good enough, not perfect. That’s a feature, not a bug. Understanding this very salient nature of abstractions is the key to designing good ones.
Interrupting my flow of reasoning with aVeryVeryLongFuncNameAndArgList is a jarring disruption. This is especially true when the function being called is actually a one-liner that can be easily inlined
Simple code isn’t necessarily the easiest code to write, and rarely is it ever the DRYest code. It takes an enormous amount of careful thought, attention to detail and care to arrive at the simplest solution that is both correct and easy to reason about.
nützlich  Meinungen  tested  Entwicklung  Projektmanagement  Programmierung  Best-Practice  Geschichte  Design 
7 weeks ago by Stolzenhain

« earlier    

related tags

*****  2017  70-533  admin  advice  analysis  api  apis  authentication  aws  azure  azurensg  backup  bash  best-practices  best  blogs  bug  buide  business  c#  career  case-study  catalogue  change  checklist  citation  clean-code  coding  collaboration  comments  comparison  configuration  css  database  design-patterns  design-principles  design  dev  development  devops  docker  documentation  engineering  entwicklung  evernote  exception-handling  feature-flags  feedly  fewd  floating-point  forms  formulare  framework  front-end  gem  geschichte  getting  git  golang  google  guide  guidelines  hardware  hiring  howto  html  http  ifttt  infrastructure  issue  it  java  javascript  jquery  js  lambda  learn  learning  library  linux  management  marketing  me  meinungen  method  metrics  minimalism  monitor  monitoring  newbs  node.js  node  nodejs  nutzerführung  nützlich  open-source  password  passwords  performance  phabricator  pocket  polyfill  postgres  postgresql  practice  process  productivity  programmierung  programming  project-management  projektmanagement  python  quality  rails  react  reactjs  readlater  reference  resources  rest  restful  ruby  rules  s3  scaling  search  secrets  security  seo  shell  sicherheit  sitecore  slider  software-development  started  startup  stripe  sysadmin  template  test  tested  testing  throttling  tips  tool  tools  tutorial  type:guide  typography  use  ux  vault  vcs  video  virtualisation  was  web-fonts  webdesign  webdev  workflow  xmpp 

Copy this bookmark: