You are a teacher of algorithms and data-structures who specializes in the use of the socratic method of teaching concepts. You build up a foundation of understanding with your student as they advance using first principles thinking. Explain the subject that the student provides to you using this approach. By default, do not explain using source code nor artifacts until the student asks for you to do so. Furthermore, do not use analysis tools. Instead, explain concepts in natural language. You are to assume the role of teacher where the teacher asks a leading question to the student. The student thinks and responds. Engage misunderstanding until the student has sufficiently demonstrated that they've corrected their thinking. Continue until the core material of a subject is completely covered. I would benefit most from an explanation style in which you frequently pause to confirm, via asking me test questions, that I've understood your explanations so far. Particularly helpful are test questions related to sim
Choose OpenBSD for your Unix needs. OpenBSD -- the world's simplest and most secure Unix-like OS. A safe alternatve to the frequent vulnerabilities and overengineering of Linux and related software (NGiNX & Apache (httpd-asiabsdcon2015.pdf), OpenSSL, iptables/nftables, systemd, BIND, Postfix, Docker etc.)
OpenBSD -- the cleanest kernel, the cleanest userland and the cleanest config
In particular the update from 2022-04-26 23:54:00 UTC
For the protection of our customers, we will not be reconnecting to GitHub until we are certain that we can do so safely, **which may take some time
| class SynchronousJob < ApplicationJob | |
| def self.perform_later | |
| raise "This job is not designed to be run asynchronously. Please use #perform_now" | |
| end | |
| end |
| /* InstantClick 3.1.0 | (C) 2014-2017 Alexandre Dieulot | http://instantclick.io/license */ | |
| var instantclick, | |
| InstantClick = (instantclick = (function(document, location, $userAgent) { | |
| // Internal variables | |
| var $currentLocationWithoutHash, | |
| $urlToPreload, | |
| $preloadTimer, | |
| $lastTouchTimestamp, | |
| $hasBeenInitialized, |
This is all you really need to know in order to make Action Mailbox work in development.
- Fire up
ngrok http 3000and make note of your subdomain for steps 3 and 8. - Create a Mailgun account because they offer sandbox addresses; grab your domain from the Dashboard.
- Go into Receiving and create a catch-all route pointing to:
https://XXX.ngrok.io/rails/action_mailbox/mailgun/inbound_emails/mime - Add your Mailgun API key to your credentials:
action_mailbox:
mailgun_api_key: API KEY HERE
| export default [ | |
| "Reticulating splines...", | |
| "Generating witty dialog...", | |
| "Swapping time and space...", | |
| "Spinning violently around the y-axis...", | |
| "Tokenizing real life...", | |
| "Bending the spoon...", | |
| "Filtering morale...", | |
| "Don't think of purple hippos...", | |
| "We need a new fuse...", |
The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.
You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.
- Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time. Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.
| require "benchmark" | |
| Benchmark.bm(7) do |bench| | |
| bench.report("single") do | |
| 1_000_000.times do | |
| 'This is a string of substantial length. I doubt you will have many string | |
| literals in your code that are longer than this, but if there are actually | |
| costs to parsing double quoted strings this should exacerbate that.' | |
| end | |
| end |