hakutsuru

Sorry if this is a bit off-topic, but sometimes it is the kid who accelerates themselves (and their parents would have no sense of the material).

Just in case you are a smart kid in high school, or helping one, Do Not Skip Calculus 1 in college based on taking the material in high school. This can be a very dangerous mistake.

If you are really confident, then get the syllabus for Calculus I from the college, and do problems from the textbook. Taking Calculus II as a first semester freshman can be very tough.

Do this only if you are confident and bored with Calculus I. Rushing foundation studies is the wrong choice for most students. I made this mistake, and thought I received honors on my engineering degree (and was a Masters student in my fourth year) -- Calculus II was the lowest grade on my transcript. Good luck.

Constraints.

More memory requires more power and weight, but portability and features restrict battery size.

Non-native languages use garbage collection, which implies 6x memory or limited performance. It is possible to emulate manual memory management, but this does not seem a common practice.

Hence, if developers write apps the standard way using web technologies, they will perform poorly on mobile devices compared with native apps.

This is primarily about ios though. Android is a different world, since it seems apps primarily use the Java ecosystem.

I feel as though I do process lists via ansible. You could be less abstract and provide code. Otherwise, it is hard to take this complaint seriously.

Here we install Jenkins jobs....

  - name: create the job config.xml files
    sudo: true
    template:
      src={{ item }}
      dest={{ conf_jenkins_home }}/jobs/{{ item | basename | replace(".xml.j2", "") }}/config.xml
      owner=jenkins
      group=jenkins
      mode=0600
    with_fileglob:
      - ../templates/jobs/*
    notify: restart Jenkins

And install SonarQube plugins...

  - name: install sonar plugins
    sudo: true
    get_url:
      url={{ item.value.url }}
      dest=/opt/sonarqube/extensions/plugins
      owner={{ ansible_ssh_user }}
      group={{ ansible_ssh_user }}
      mode=0755
    with_dict: "{{ sonarqube_plugins }}"

Columbia House was a multi-format business, very sensitive to "hits", which experienced booms when new formats were being adopted. It catered to collectors, not with "quality" per se, but convenience and bargains.

(Recognizing the weird/sleazy negative-option element, it was possible to use Columbia House to amass product at a discount while playing by the rules, as explain by others.)

The CD boom pushed the company toward $2 Billion annual revenue. Take these numbers as fuzzy. Revenue definitely dropped, but it was still sizable for music, though the music clubs became much less profitable...

When Bertelsmann acquired Columbia House to eliminate the competition for BMG, the music clubs were shut down. While I can sympathize with people calling Columbia House a failed business, its music business did not fail.

Yes, and the wiki is relevant... Columbia House, BMG and Bookspan were mashed together years ago. While Columbia House could a Dilbertesque nightmare, the Machiavellianism I watched unfold in Garden City was remarkable.

While this may have been so at some time, while I was at the company (1998-2010), it is categorically false.

Fraud detection became an important kpi, and sophisticated tools were used to minimize it. The company was shopped and acquired several times, due diligence for the business model would not allow outright fraud like this to survive. I appreciate the cynicism though.

Another example of manual processing done on the warehouse side was manually entering in pricing from the print catalogs, to honor pricing mistakes. Such mistakes cost the company millions of dollars, but I eliminated them by automating print segment pricing (via 4D, AppleScript and Em Software plugins).

An important element of the business which might not be appreciated is that members were segmented, so each cycle several versions of the "monthly" catalog were created, with pricing tailored to the segment ("in commit", "out of commit", etc).

I would not propose this book as one that every programmer should read. But others have posted about books that started with fundamentals and illustrated how computing systems evolved, which brings this book to mind... Henry D'Angelo "Microcomputer Structures".

"Microcomputer Structures" is out-of-print, but I recall the small text starting with atomic physics and building up to an introduction of the Von Neumann architecture.

As a freshman at Boston University in the 1980's, I took this mind-expanding course (probably because it was way above my level) with Professor D'Angelo. The final project was building an interface to a single-board computer.