programming   1247488

« earlier    

Top Data Science Skills In 2017: Identify Where to Work and the Skills to Land You There
In today’s article, I’m going to research some job listings at LinkedIn’s top 3 companies and then tell you what these listings reveal about the top data science skills in 2017.
data  programming 
19 hours ago by drilltotheheavens
Why We Argue: Style - Sandi Metz
"Code is read many more times than it is written, which means that the ultimate cost of code is in its reading."
programming 
20 hours ago by dusko
Becoming a 10x Data Scientist - Algorithmia
Borrowing tips and tricks from software developers, learn how to create a more productive workflow on the journey to becoming a 10X Data Scientist.
career  data-science  datascience  programming  datascientist  data_science  developer 
20 hours ago by morganwatch
Whose bug is this anyway?!? - Code Of Honor
<<
During the development of Guild Wars (GW) I had occasion to review many bug reports sent in from players’ computers. As GW players may remember, in the (hopefully unlikely) event that the game crashed it would offer to send the bug report back to our “lab” for analysis. When we received those bug reports we triaged to determine who should handle each report, but of course bugs come in all manner of shapes and sizes and some don’t have a clear owner, so several of us would take turns at fixing these bugs.

Periodically we’d come across bugs that defied belief and we’d be left scratching our heads. While it wasn’t impossible for the bugs to occur, and we could construct hypothetically plausible explanations that didn’t involve redefining the space-time continuum, they just “shouldn’t” have occurred. It was possible they could be memory corruption or thread race issues, but given the information we had it just seemed unlikely.

Mike O’Brien, one of the co-founders and a crack programmer, eventually came up with the idea that they were related to computer hardware failures rather than programming failures. More importantly he had the bright idea for how to test that hypothesis, which is the mark of an excellent scientist.

He wrote a module (“OsStress”) which would allocate a block of memory, perform calculations in that memory block, and then compare the results of the calculation to a table of known answers. He encoded this stress-test into the main game loop so that the computer would perform this verification step about 30-50 times per second.

On a properly functioning computer this stress test should never fail, but surprisingly we discovered that on about 1% of the computers being used to play Guild Wars it did fail! One percent might not sound like a big deal, but when one million gamers play the game on any given day that means 10,000 would have at least one crash bug. Our programming team could spend weeks researching the bugs for just one day at that rate!
>>

Memo to self: if I ever develop client software for >1M weekly actives, try hard to allocate some resources to ship a hack like this.
programming  faults-in-computing-machinery  hardware  software 
20 hours ago by absfac
Fix8 Open Source FIX Engine
High Performance C++ FIX Framework
programming  fix  finance  c++ 
21 hours ago by Z303

« earlier    

related tags

a+  aggregator  agile  ai  algorithms  analysis  api  app  apps  arrow  article  ast  asyncio  automation  autoupdate  awsome  basic  best-practices  bestpractices  bind  blockchain  blog  book  books  c++  c  capitalism  career  category_theory  cheatsheet  ci  clojure  clojurescript  code  coding  communication  community  compassionate.coding  compiler  compilers  computer  computerscience  cool  coursera  courseware  cpp  cs  css  data-science  data  data_science  database  datascience  datascientist  datastructures  db  design-patterns  design  developer  development  directory  documentation  dotnet  ebook  editor  education  engineering  explanation  f#  fable  faults-in-computing-machinery  favorites  finance  fix  flow  focus  font  fonts  framework  free  fun-programming  fun  function  functional  game-engine  game  gamedev  games  gaming  gis  github  go  golang  google  graal  graalvm  graphics  guide  hackernews  hardware  hdr  hippocratic.oath  history  hn  howto  ibm  ide  info-foraging  info  interesting  internals  international  interpreter  intro  ios  iphone  iteration-recursion  java  javascript  jit  js  json  jvm  kotlin  labor  language  languages  laravel  learn  learning  library  lifehacks  linux  list  llvm  machinelearning  management  maps  market  markets  math  microsoft  mindfulness  minimalism  mooc  music  mvc  natural.language  news  nlp  nodejs  notebook  onlinetools  opensource  osx  patterns  performance  perl  philosophy  php  plt  podcasts  posix  problems  productivity  progressive-enhancement  publishing  python  python3  q-n-a  qbasic  r  react  refactoring  reference  rendering  repository  research  resource  rest  richclient  robpike  rpg  ruby  scala  school  schools  security  sep17  simplicity  slack  software  spotify  sql  stackex  statistics  style  suave  swift  swtool  teams  tech  technology  terminal  text  tips  todo  toolkit  trivia  truffle  tutorial  twitter  typography  unix  usenet  video  vim  visualization  warelogging  web  webapplication  webdesign  webdev  webkit  wiki  windows  work  workflow  working-remotely  wqebdev  xcode  yak-shaving 

Copy this bookmark:



description:


tags: