nhaliday + guide   144

Introduction · CTF Field Guide
also has some decent looking career advice and links to books/courses if I ever get interested in infosec stuff
guide  security  links  list  recommendations  contest  puzzles  hacker  init  adversarial  systems  traces  accretion  programming  debugging  assembly  c(pp)  metal-to-virtual  career  planning  jobs  books  course  learning  threat-modeling  tech  working-stiff 
8 days ago by nhaliday
Ask HN: Learning modern web design and CSS | Hacker News
Ask HN: Best way to learn HTML and CSS for web design?: https://news.ycombinator.com/item?id=11048409
Ask HN: How to learn design as a hacker?: https://news.ycombinator.com/item?id=8182084

Ask HN: How to learn front-end beyond the basics?: https://news.ycombinator.com/item?id=19468043
Ask HN: What is the best JavaScript stack for a beginner to learn?: https://news.ycombinator.com/item?id=8780385
Free resources for learning full-stack web development: https://news.ycombinator.com/item?id=13890114

Ask HN: What is essential reading for learning modern web development?: https://news.ycombinator.com/item?id=14888251
Ask HN: A Syllabus for Modern Web Development?: https://news.ycombinator.com/item?id=2184645

Ask HN: Modern day web development for someone who last did it 15 years ago: https://news.ycombinator.com/item?id=20656411
hn  discussion  design  form-design  frontend  web  tutorial  links  recommendations  init  pareto  efficiency  minimum-viable  move-fast-(and-break-things)  advice  roadmap  multi  hacker  games  puzzles  learning  guide  dynamic  retention  DSL  working-stiff  q-n-a  javascript  frameworks  ecosystem  libraries  client-server  hci  ux  books  chart 
8 weeks ago by nhaliday
[Tutorial] A way to Practice Competitive Programming : From Rating 1000 to 2400+ - Codeforces
this guy really didn't take that long to reach red..., as of today he's done 20 contests in 2y to my 44 contests in 7y (w/ a long break)...>_>

tho he has 3 times as many submissions as me. maybe he does a lot of virtual rounds?

some snippets from the PDF guide linked:
1400-1900:
To be rating 1900, skills as follows are needed:
- You know and can use major algorithms like these:
Brute force DP DFS BFS Dijkstra
Binary Indexed Tree nCr, nPr Mod inverse Bitmasks Binary Search
- You can code faster (For example, 5 minutes for R1100 problems, 10 minutes for
R1400 problems)

If you are not good at fast-coding and fast-debugging, you should solve AtCoder problems. Actually, and statistically, many Japanese are good at fast-coding relatively while not so good at solving difficult problems. I think that’s because of AtCoder.

I recommend to solve problem C and D in AtCoder Beginner Contest. On average, if you can solve problem C of AtCoder Beginner Contest within 10 minutes and problem D within 20 minutes, you are Div1 in FastCodingForces :)

...

Interestingly, typical problems are concentrated in Div2-only round problems. If you are not good at Div2-only round, it is likely that you are not good at using typical algorithms, especially 10 algorithms that are written above.

If you can use some typical problem but not good at solving more than R1500 in Codeforces, you should begin TopCoder. This type of practice is effective for people who are good at Div.2 only round but not good at Div.1+Div.2 combined or Div.1+Div.2 separated round.

Sometimes, especially in Div1+Div2 round, some problems need mathematical concepts or thinking. Since there are a lot of problems which uses them (and also light-implementation!) in TopCoder, you should solve TopCoder problems.

I recommend to solve Div1Easy of recent 100 SRMs. But some problems are really difficult, (e.g. even red-ranked coder could not solve) so before you solve, you should check how many percent of people did solve this problem. You can use https://competitiveprogramming.info/ to know some informations.

1900-2200:
To be rating 2200, skills as follows are needed:
- You know and can use 10 algorithms which I stated in pp.11 and segment trees
(including lazy propagations)
- You can solve problems very fast: For example, 5 mins for R1100, 10 mins for
R1500, 15 mins for R1800, 40 mins for R2000.
- You have decent skills for mathematical-thinking or considering problems
- Strong mental which can think about the solution more than 1 hours, and don’t give up even if you are below average in Div1 in the middle of the contest

This is only my way to practice, but I did many virtual contests when I was rating 2000. In this page, virtual contest does not mean “Virtual Participation” in Codeforces. It means choosing 4 or 5 problems which the difficulty is near your rating (For example, if you are rating 2000, choose R2000 problems in Codeforces) and solve them within 2 hours. You can use https://vjudge.net/. In this website, you can make virtual contests from problems on many online judges. (e.g. AtCoder, Codeforces, Hackerrank, Codechef, POJ, ...)

If you cannot solve problem within the virtual contests and could not be able to find the solution during the contest, you should read editorial. Google it. (e.g. If you want to know editorial of Codeforces Round #556 (Div. 1), search “Codeforces Round #556 editorial” in google) There is one more important thing to gain rating in Codeforces. To solve problem fast, you should equip some coding library (or template code). For example, I think that equipping segment tree libraries, lazy segment tree libraries, modint library, FFT library, geometry library, etc. is very effective.

2200 to 2400:
Rating 2200 and 2400 is actually very different ...

To be rating 2400, skills as follows are needed:
- You should have skills that stated in previous section (rating 2200)
- You should solve difficult problems which are only solved by less than 100 people in Div1 contests

...

At first, there are a lot of educational problems in AtCoder. I recommend you should solve problem E and F (especially 700-900 points problem in AtCoder) of AtCoder Regular Contest, especially ARC058-ARC090. Though old AtCoder Regular Contests are balanced for “considering” and “typical”, but sadly, AtCoder Grand Contest and recent AtCoder Regular Contest problems are actually too biased for considering I think, so I don’t recommend if your goal is gain rating in Codeforces. (Though if you want to gain rating more than 2600, you should solve problems from AtCoder Grand Contest)

For me, actually, after solving AtCoder Regular Contests, my average performance in CF virtual contest increased from 2100 to 2300 (I could not reach 2400 because start was early)

If you cannot solve problems, I recommend to give up and read editorial as follows:
Point value 600 700 800 900 1000-
CF rating R2000 R2200 R2400 R2600 R2800
Time to editorial 40 min 50 min 60 min 70 min 80 min

If you solve AtCoder educational problems, your skills of competitive programming will be increased. But there is one more problem. Without practical skills, you rating won’t increase. So, you should do 50+ virtual participations (especially Div.1) in Codeforces. In virtual participation, you can learn how to compete as a purple/orange-ranked coder (e.g. strategy) and how to use skills in Codeforces contests that you learned in AtCoder. I strongly recommend to read editorial of all problems except too difficult one (e.g. Less than 30 people solved in contest) after the virtual contest. I also recommend to write reflections about strategy, learns and improvements after reading editorial on notebooks after the contests/virtual.

In addition, about once a week, I recommend you to make time to think about much difficult problem (e.g. R2800 in Codeforces) for couple of hours. If you could not reach the solution after thinking couple of hours, I recommend you to read editorial because you can learn a lot. Solving high-level problems may give you chance to gain over 100 rating in a single contest, but also can give you chance to solve easier problems faster.
oly  oly-programming  problem-solving  learning  practice  accretion  strategy  hmm  pdf  guide  reflection  advice  wire-guided  marginal  stylized-facts  speed  time  cost-benefit  tools  multi  sleuthin  review  comparison  puzzles  contest  aggregator  recommendations  objektbuch  time-use  growth  studying  🖥  👳  yoga 
august 2019 by nhaliday
How to work with GIT/SVN — good practices - Jakub Kułak - Medium
best part of this is the links to other guides
Commit Often, Perfect Later, Publish Once: https://sethrobertson.github.io/GitBestPractices/

My Favourite Git Commit: https://news.ycombinator.com/item?id=21289827
I use the following convention to start the subject of commit(posted by someone in a similar HN thread):
...
org:med  techtariat  tutorial  faq  guide  howto  workflow  devtools  best-practices  vcs  git  engineering  programming  multi  reference  org:junk  writing  technical-writing  hn  commentary  jargon  list  objektbuch  examples  analysis 
june 2019 by nhaliday
C++ Core Guidelines
This document is a set of guidelines for using C++ well. The aim of this document is to help people to use modern C++ effectively. By “modern C++” we mean effective use of the ISO C++ standard (currently C++17, but almost all of our recommendations also apply to C++14 and C++11). In other words, what would you like your code to look like in 5 years’ time, given that you can start now? In 10 years’ time?

https://isocpp.github.io/CppCoreGuidelines/
“Within C++ is a smaller, simpler, safer language struggling to get out.” – Bjarne Stroustrup

...

The guidelines are focused on relatively higher-level issues, such as interfaces, resource management, memory management, and concurrency. Such rules affect application architecture and library design. Following the rules will lead to code that is statically type safe, has no resource leaks, and catches many more programming logic errors than is common in code today. And it will run fast - you can afford to do things right.

We are less concerned with low-level issues, such as naming conventions and indentation style. However, no topic that can help a programmer is out of bounds.

Our initial set of rules emphasize safety (of various forms) and simplicity. They may very well be too strict. We expect to have to introduce more exceptions to better accommodate real-world needs. We also need more rules.

...

The rules are designed to be supported by an analysis tool. Violations of rules will be flagged with references (or links) to the relevant rule. We do not expect you to memorize all the rules before trying to write code.

contrary:
https://aras-p.info/blog/2018/12/28/Modern-C-Lamentations/
This will be a long wall of text, and kinda random! My main points are:
1. C++ compile times are important,
2. Non-optimized build performance is important,
3. Cognitive load is important. I don’t expand much on this here, but if a programming language or a library makes me feel stupid, then I’m less likely to use it or like it. C++ does that a lot :)
programming  engineering  pls  best-practices  systems  c(pp)  guide  metabuch  objektbuch  reference  cheatsheet  elegance  frontier  libraries  intricacy  advanced  advice  recommendations  big-picture  novelty  lens  philosophy  state  error  types  concurrency  memory-management  performance  abstraction  plt  compilers  expert-experience  multi  checking  devtools  flux-stasis  safety  system-design  techtariat  time  measure  dotnet  comparison  examples  build-packaging  thinking  worse-is-better/the-right-thing  cost-benefit  tradeoffs  essay  commentary  oop  correctness  computer-memory  error-handling  resources-effects  latency-throughput 
june 2019 by nhaliday
package writing - Where do I start LaTeX programming? - TeX - LaTeX Stack Exchange
I think there are three categories which need to be mastered (perhaps not all in the same degree) in order to become comfortable around TeX programming:

1. TeX programming. That's very basic, it deals with expansion control, counters, scopes, basic looping constructs and so on.

2. TeX typesetting. That's on a higher level, it includes control over boxes, lines, glues, modes, and perhaps about 1000 parameters.

3. Macro packages like LaTeX.
q-n-a  stackex  programming  latex  howto  nitty-gritty  yak-shaving  links  list  recommendations  books  guide  DSL 
may 2019 by nhaliday
documentation - Materials for learning TikZ - TeX - LaTeX Stack Exchange
The way I learned all three was basically demand-driven --- "learning by doing". Whenever I needed something "new", I'd dig into the manual and try stuff until either it worked (not always most elegantly), or in desperation go to the examples website, or moan here on TeX-'n-Friends. Occasionally supplemented by trying to answer "challenging" questions here.

yeah I kinda figured that was the right approach. just not worth the time to be proactive.
q-n-a  stackex  latex  list  links  tutorial  guide  learning  yak-shaving  recommendations  programming  visuo  dataviz  prioritizing  technical-writing 
may 2019 by nhaliday
Introduction to Scaling Laws
https://betadecay.wordpress.com/2009/10/02/the-physics-of-scaling-laws-and-dimensional-analysis/
http://galileo.phys.virginia.edu/classes/304/scaling.pdf

Galileo’s Discovery of Scaling Laws: https://www.mtholyoke.edu/~mpeterso/classes/galileo/scaling8.pdf
Days 1 and 2 of Two New Sciences

An example of such an insight is “the surface of a small solid is comparatively greater than that of a large one” because the surface goes like the square of a linear dimension, but the volume goes like the cube.5 Thus as one scales down macroscopic objects, forces on their surfaces like viscous drag become relatively more important, and bulk forces like weight become relatively less important. Galileo uses this idea on the First Day in the context of resistance in free fall, as an explanation for why similar objects of different size do not fall exactly together, but the smaller one lags behind.
nibble  org:junk  exposition  lecture-notes  physics  mechanics  street-fighting  problem-solving  scale  magnitude  estimate  fermi  mental-math  calculation  nitty-gritty  multi  scitariat  org:bleg  lens  tutorial  guide  ground-up  tricki  skeleton  list  cheatsheet  identity  levers  hi-order-bits  yoga  metabuch  pdf  article  essay  history  early-modern  europe  the-great-west-whale  science  the-trenches  discovery  fluid  architecture  oceans  giants  tidbits  elegance 
august 2017 by nhaliday
How accurate are population forecasts?
2 The Accuracy of Past Projections: https://www.nap.edu/read/9828/chapter/4
good ebook:
Beyond Six Billion: Forecasting the World's Population (2000)
https://www.nap.edu/read/9828/chapter/2
Appendix A: Computer Software Packages for Projecting Population
https://www.nap.edu/read/9828/chapter/12
PDE Population Projections looks most relevant for my interests but it's also *ancient*
https://applieddemogtoolbox.github.io/Toolbox/
This Applied Demography Toolbox is a collection of applied demography computer programs, scripts, spreadsheets, databases and texts.

How Accurate Are the United Nations World Population Projections?: http://pages.stern.nyu.edu/~dbackus/BCH/demography/Keilman_JDR_98.pdf

cf. Razib on this: https://pinboard.in/u:nhaliday/b:d63e6df859e8
news  org:lite  prediction  meta:prediction  tetlock  demographics  population  demographic-transition  fertility  islam  world  developing-world  africa  europe  multi  track-record  accuracy  org:ngo  pdf  study  sociology  measurement  volo-avolo  methodology  estimate  data-science  error  wire-guided  priors-posteriors  books  guide  howto  software  tools  recommendations  libraries  gnxp  scitariat 
july 2017 by nhaliday
The Internet Guide to Funding College and Section 529 College Savings Plans. Savingforcollege.com
https://twitter.com/toad_spotted/status/882227467263586304
https://archive.is/AYsxl
It looks to me like best thing to do is accrue home equity (since it's partly shielded for financial aid purposes)&otherwise grin n bear it
It's pretty obvious that the 521 break mostly is a transfer from federal government to colleges and state budgets not to rich households.
personal-finance  investing  parenting  higher-ed  money  temperance  howto  reference  database  guide  human-bean  multi  twitter  social  commentary  ratty  unaffiliated  housing  backup  org:fin 
april 2017 by nhaliday
Edge Master Class 2008 RICHARD THALER, SENDHIL MULLAINATHAN, DANIEL KAHNEMAN: A SHORT COURSE IN BEHAVIORAL ECONOMICS | Edge.org
https://twitter.com/toad_spotted/status/878990195953205248
huge popularity of "behavioral economics"among powerful people=largely excitement at how much more control they'd exert over stupider people

Time for Behavioral Political Economy? An Analysis of Articles in Behavioral Economics: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1846184
This study analyzes leading research in behavioral economics to see whether it contains advocacy of paternalism and whether it addresses the potential cognitive limitations and biases of the policymakers who are going to implement paternalist policies. The findings reveal that 20.7% of the studied articles in behavioral economics propose paternalist policy action and that 95.5% of these do not contain any analysis of the cognitive ability of policymakers. This suggests that behavioral political economy, in which the analytical tools of behavioral economics are applied to political decision-makers as well, would offer a useful extension of the research program.

https://www.bloomberg.com/view/articles/2017-07-19/some-countries-like-nudges-more-than-others
Research shows that Americans and conservatives can be less open to cues to change behavior.

It’s For Your Own Good!: http://www.nybooks.com/articles/2013/03/07/its-your-own-good/
- Cass Sunstein

Against Autonomy: Justifying Coercive Paternalism
by Sarah Conly
Cambridge University Press, 206 pp., $95.00

WHO NUDGES THE NUDGERS?: https://jacobitemag.com/2017/10/26/who-nudges-the-nudgers/
org:edge  guide  video  lectures  list  expert  economics  behavioral-econ  psychology  cog-psych  unit  complex-systems  🎩  multi  twitter  social  discussion  ratty  unaffiliated  aphorism  hmm  lol  authoritarianism  managerial-state  microfoundations  news  org:mag  org:biz  org:bv  journos-pundits  technocracy  books  review  expert-experience  elite  vampire-squid  study  lmao  data  info-dynamics  error  biases  iq  distribution  pro-rata  impetus  crooked  antidemos  civil-liberty  randy-ayndy  political-econ  gnon  org:popup  paying-rent  incentives  government  world  usa  alien-character  allodium  old-anglo  big-peeps  humility  noblesse-oblige  institutions  interests  org:local  utopia-dystopia 
february 2017 by nhaliday
How to do career planning properly - 80,000 Hours
- A/B/Z plans
- make a list of red flags and commit to reviewing at some point (and at some interval)
advice  strategy  career  planning  80000-hours  long-term  thinking  guide  summary  checklists  rat-pack  tactics  success  working-stiff  flexibility  wire-guided  progression  ratty 
november 2016 by nhaliday
« earlier      
per page:    204080120160

bundles : initmeta

related tags

80000-hours  :/  abortion-contraception-embryo  abstraction  academia  accretion  accuracy  acm  acmtariat  advanced  adversarial  advice  africa  aggregator  aging  agriculture  ai  ai-control  akrasia  algorithms  alien-character  alignment  allodium  altruism  analysis  anomie  antidemos  aphorism  api  apple  applications  architecture  arms  arrows  article  assembly  atoms  attention  authoritarianism  automation  backup  bare-hands  behavioral-econ  behavioral-gen  ben-recht  benchmarks  berkeley  best-practices  better-explained  biases  big-peeps  big-picture  bio  biodet  biohacking  bioinformatics  biotech  bitcoin  blockchain  blog  blowhards  books  bostrom  brands  browser  buddhism  build-packaging  business  c(pp)  c:**  caching  calculation  california  capital  cardio  career  CAS  causation  chan  chapman  chart  cheatsheet  checking  checklists  chemistry  civic  civil-liberty  clarity  classification  client-server  cloud  cmu  coarse-fine  cocoa  code-dive  code-organizing  cog-psych  commentary  comparison  compensation  competition  compilers  complex-systems  composition-decomposition  computer-memory  computer-vision  concept  concurrency  config  confluence  confounding  consumerism  contest  contrarianism  cooking  cool  cooperate-defect  coordination  correctness  corruption  cost-benefit  coupling-cohesion  course  cracker-prog  CRISPR  critique  crooked  cryptocurrency  cs  culture  d-lang  data  data-science  data-structures  database  dataset  dataviz  dbs  debugging  decision-making  decision-theory  deep-learning  degrees-of-freedom  demographic-transition  demographics  descriptive  design  desktop  detail-architecture  deterrence  developing-world  devops  devtools  diet  differential  dimensionality  diogenes  direct-indirect  dirty-hands  discipline  discovery  discussion  distributed  distribution  divide-and-conquer  diy  documentation  dotnet  DP  draft  drugs  DSL  duplication  dynamic  dysgenics  early-modern  economics  econotariat  ecosystem  editors  education  effective-altruism  efficiency  elections  elegance  elite  embedded  embodied  embodied-pack  embodied-street-fighting  engineering  enhancement  ensembles  entrepreneurialism  epistemic  erik-demaine  error  error-handling  essay  estimate  ethics  europe  evidence-based  examples  expert  expert-experience  explanation  exposition  externalities  extrema  facebook  faq  features  fermi  fertility  finance  fisher  fitness  fitsci  flexibility  fluid  flux-stasis  focus  food  foreign-lang  foreign-policy  form-design  formal-methods  frameworks  free  french  frontend  frontier  functional  futurism  game-theory  games  gbooks  gelman  generalization  genetic-correlation  genetics  genomics  geoengineering  geometry  giants  gilens-page  git  gnon  gnu  gnxp  golang  google  gotchas  government  grad-school  gradient-descent  graphics  graphs  grokkability  grokkability-clarity  ground-up  growth  guide  GWAS  gwern  h2o  hacker  haidt  hardware  hashing  haskell  hci  health  heavyweights  heuristic  hi-order-bits  high-variance  higher-ed  history  hmm  hn  housing  howto  huge-data-the-biggest  human-bean  human-capital  humility  hypochondria  hypothesis-testing  ideas  identity  ideology  idk  IEEE  impact  impetus  incentives  info-dynamics  info-foraging  information-theory  inhibition  init  input-output  insight  institutions  integration-extension  intellectual-property  interests  interface-compatibility  internet  interpretability  intervention  interview-prep  intricacy  intuition  investing  iq  islam  iteration-recursion  jargon  javascript  jobs  journos-pundits  jvm  kaggle  keyboard  knowledge  labor  language  latency-throughput  latex  latin-america  law  learning  lecture-notes  lectures  len:long  lens  let-me-see  levers  lexical  libraries  linear-algebra  linearity  links  linux  list  llvm  lmao  lol  long-short-run  long-term  longevity  longform  machine-learning  macro  madisonian  magnitude  maker  management  managerial-state  manifolds  marginal  math  math.DS  measure  measurement  mechanics  memory-management  mendel-randomization  mental-math  meta:prediction  meta:war  metabolic  metabuch  metal-to-virtual  methodology  metrics  michael-nielsen  microbiz  microfoundations  mindful  minimalism  minimum-viable  missing-heritability  model-class  money  money-for-time  mooc  morality  mostly-modern  move-fast-(and-break-things)  multi  music  music-theory  nature  navigation  negotiation  network-structure  networking  neurons  new-religion  news  nibble  nihil  nitty-gritty  no-go  noblesse-oblige  nonlinearity  nootropics  notation  novelty  nuclear  numerics  nutrition  objektbuch  ocaml-sml  oceans  ocr  old-anglo  oly  oly-programming  oop  openai  operational  optimization  orders  ORFE  org:biz  org:bleg  org:bv  org:com  org:edge  org:edu  org:fin  org:gov  org:health  org:junk  org:lite  org:local  org:mag  org:med  org:ngo  org:popup  organization  os  oss  osx  outdoors  p2p  p:whenever  parenting  pareto  parsimony  paste  paying-rent  pdf  peace-violence  performance  personal-finance  phd  philosophy  physics  pinboard  piracy  planning  plots  pls  plt  polarization  policy  polisci  political-econ  politics  population  postrat  practice  pragmatic  prediction  prepping  prioritizing  priors-posteriors  pro-rata  problem-solving  productivity  programming  progression  project  property-rights  protocol-metadata  psychology  public-health  publishing  puzzles  python  q-n-a  quality  quantified-self  quantitative-qualitative  quixotic  quotes  r-lang  random  randy-ayndy  ranking  rat-pack  ratty  reading  realness  recommendations  recruiting  reference  reflection  regularization  regularizer  reinforcement  religion  rent-seeking  replication  repo  research  resources-effects  retention  retrofit  review  rhetoric  rhythm  rigidity  risk  roadmap  roots  rsc  ruby  rust  s:*  safety  sample-complexity  scale  scaling-tech  scaling-up  scaruffi  scholar  sci-comp  science  scitariat  search  sebastien-bubeck  securities  security  selection  sequential  serene  shipping  sib-study  signal-noise  simplification-normalization  skeleton  sleep  sleuthin  social  social-psych  social-science  society  sociology  software  space  span-cover  spanish  speaking  speed  speedometer  spreading  stackex  stanford  startups  state  stats  strategy  stream  street-fighting  stress  strings  stripe  study  studying  stylized-facts  success  summary  summer-2014  supply-demand  survey  survival  sv  syntax  synthesis  system-design  systems  tactics  tails  tcs  tcstariat  teaching  tech  tech-infrastructure  technical-writing  technocracy  technology  techtariat  temperance  terminal  tetlock  the-great-west-whale  the-trenches  the-west  the-world-is-just-atoms  theos  things  thinking  threat-modeling  tidbits  time  time-use  tip-of-tongue  todo  tools  top-n  toxoplasmosis  toys  traces  track-record  tradeoffs  transitions  travel  trees  tribalism  tricki  tricks  tutorial  twitter  types  ubiquity  ui  unaffiliated  uncertainty  unit  unix  unsupervised  urban  urban-rural  usa  utopia-dystopia  ux  values  vampire-squid  vc-dimension  vcs  video  virtu  visual-understanding  visuo  volo-avolo  vulgar  war  waves  web  white-paper  wiki  wire-guided  wonkish  workflow  working-stiff  world  world-war  worrydream  worse-is-better/the-right-thing  writing  yak-shaving  yoga  🌞  🎓  🎩  🐸  👳  🔬  🖥  🦉 

Copy this bookmark:



description:


tags: