At the end of trying out BFG to purge a large compiled file from a repo, the following message was displayed:
😀
—
You can rewrite history in Git – don’t let Trump do it for real!
Trump’s administration has lied consistently, to make people give up on ever
being told the truth. Don’t give up: https://github.com/bkeepers/stop-trump
—
So with git, one no longer needs to be a rhetor to change the past.
I wonder how many people truly find the user experience compelling or merely stay put because all their friends are there.
Back in the good old days when I was working as a GPU architect in NVIDIA, we had suites of tests for various stages of GPU development: architecture, RTL, driver, real chips, etc.
Ogtest, consisting of tests written in OpenGL, can be applied to all stages. Each test is written to be as compact as possible, the tests are ordered from simple to complex, and collectively they cover the entire target space (e.g. all applications to run on the target GPU).
For example, the first test is to draw a flat colored triangle, the next is a textured triangle, and the next is called son-of-the-textured-triangle (with two textures instead of just one, if I remember correctly).
I then went on to add a test called daughter-of-the-textured-triangle (I am all in for gender equality) which consists of two textures but exercised a different path through the texturing and shading units (if I remember correctly).
I like to think of these as the basis test cases for the entire target space, analogous to basis vectors in linear algebra.
This applies to all research and development projects. Instead of jumping to debug full-scale applications, it can help to design a set of basis cases first. The process can clarify our thinking, and help us debug and explore algorithm/implementation issues. The basis cases can even be part of the analysis section of a research paper.
In the process of migrating some svn repos on my server to git repos on github (public) and bitbucket (private), I found the following migration process works well.
. Import the svn repo to github. It worked for private svn repos that require authentication (as in my case).
. The github repo will be public. If you want a private repo, import the github repo to a private bitbucket repo, and delete the public github repo.
I looked at the revision history and it appears to be well preserved.
I have tried direct import from svn to bitbucket but it did not work, probably due to file system structures of my svn server.
Few people have the time and patience to answer surveys, even when they do they might not provide genuine opinions (consciously or not), and the sampling is inherently biased.
A well designed system collects data and analyzes users on the go; just look at Google, Facebook, and Amazon.
Algorithms can already devise algorithms and write programs.
It is just a matter of time before they can do that in a scale massive enough to displace many, if not most, programming jobs, just like what robots have already done to the manufacturing jobs.
I found inspirations from this Q/A session between Sam Altman and Michael Moritz not only for startups but anyone who needs to deal with an ever changing environment: do not sit on the past, keep a fresh team, and change with the future.
Theme: Rubric. Get a free blog at WordPress.com
