| name | explain-diff-html |
|---|---|
| description | Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output. |
Please make me a rich, interactive explanation of the specified code change.
It should have these sections:
Many users of Git are curious about the lack of delta compression at the object (blob) level when commits are first written. This efficiency is saved until the pack file is written. Loose objects are written in compressed, but non-delta format at the time of each commit.
A simple run though of a commit sequence with only the smallest change to the image (in uncompressed TIFF format to amplify the observable behavior) aids the understanding of this deferred and different approach efficiency.
Create the repo:
...and obviously we're building a workaround. But I'm absolutely flabbergasted that a standard <input type="date"> HTML field, in a standard browser, from a company that bases its reputation good design, could be so dreadful.
I'm the developer for a startup that sells a genetic test to recommend medications for high blood pressure. As such, most of our customers are in their 60s or older. We have found that many of them are using iPads or iPhones. And they're the ones complaining to our customer support line about our site being unusable.
This is what pops up when you tap on a date field. Not bad... unless you're trying to pick your birth date, which happened to be in 1945.
| 'use strict'; | |
| var React = require('react'); | |
| var ReactNative = require('react-native'); | |
| var {AppRegistry, Text, WebView, View, Dimensions} = ReactNative; | |
| var WebViewResizing = React.createClass({ | |
| getInitialState: function () { | |
| return { | |
| webViewHeight: 100 // default height, can be anything |
| # .github/workflows/app.yaml | |
| name: My Python Project | |
| on: push | |
| jobs: | |
| test: | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 10 | |
| services: |
| <html> | |
| <body> | |
| <header>header</header> | |
| <main id="main">main</main> | |
| <footer>footer</footer> | |
| </body> | |
| </html> |
I'm Jesse, one of the co-founders of Dev Bootcamp, and the acting curricular editor-in-chief. We get lots of questions about how Dev Bootcamp approaches teaching, what our curriculum is like, and how it differs from other schools and competitors. I thought I'd share some of that with you, starting with a brief overview of our theory of learning and then sharing our introduction to ActiveRecord.
This will be light on theory and heavy on ActiveRecord, so if you're not familiar with SQL or Ruby it might be hard to follow. Mea culpa.
At Dev Bootcamp, we believe that "modeling" is central to learning. The most effective students have a clear model of how the world works and are able to quickly integrate new information int
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| //Based on gulpfile.js from Google Web Starter Kit. | |
| //https://github.com/google/web-starter-kit | |
| 'use strict'; | |
| // Include Gulp & Tools We'll Use | |
| var gulp = require('gulp'); | |
| var $ = require('gulp-load-plugins')(); | |
| var del = require('del'); | |
| var runSequence = require('run-sequence'); | |
| var browserSync = require('browser-sync'); |
| from snake import * | |
| import pyperclip | |
| from sh import xdotool | |
| import random | |
| import string | |
| @key_map("<leader>l") | |
| def log(): | |
| ''' |