Write copy that converts. Landing pages, emails, sales copy, headlines, CTAs, social posts — anything persuasive.
This is an AI skill file. It turns any AI into a direct response copywriter trained on the frameworks of Schwartz, Hopkins, Ogilvy, Halbert, Caples, Sugarman, and Collier. Instead of getting generic AI copy, you get internet-native writing that sounds like a smart friend explaining something — while quietly deploying every persuasion principle in the book.
This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.
I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.
But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.
If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.
| # archive of https://blog.wplauncher.com/convert-heic-to-jpg-on-mac/ | |
| Step 1: Install Homebrew | |
| Open up your terminal by clicking on your spacebar and the command key at the same time, then type in terminal, and then click on Terminal.app to open it up. | |
| If you’re not used to using your Terminal, it may seem a little intimidating and may make you nervous, but don’t worry this is completely safe. Homebrew is a package manager for macOS, in other words, it installs the stuff you need that Apple didn’t install. You can learn more about Homebrew here. | |
| Once Terminal has opened, run the following command inside of it: |
While attempting to explain JavaScript's reduce method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.
JavaScript Arrays have lots of built in methods on their prototype. Some of them mutate - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, List is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a new list - thus making it much simpler to think about both the old list and the new one, what they contain, and
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| /* | |
| In JavaScript, objects can be used to serve various purposes. | |
| To maximise our usage of the type system, we should assign different types to our objects depending | |
| on the desired purpose. | |
| In this blog post I will clarify two common purposes for objects known as records and dictionaries | |
| (aka maps), and how they can both be used with regards to the type system. |
| @199rec.co.uk | |
| @24-7recruitment.net | |
| @2kpeople.co.uk | |
| @33six.net | |
| @365rec.com | |
| @3aaa.co.uk | |
| @3rglobal.com | |
| @48digital.co.uk | |
| @4itrecruitment.co.uk | |
| @752solutions.com |
| /** | |
| * Definition for a binary tree node. | |
| * function TreeNode(val) { | |
| * this.val = val; | |
| * this.left = this.right = null; | |
| * } | |
| */ | |
| /** | |
| * @param {TreeNode} root | |
| * @return {number} |
| tldr; | |
| DDD is primarily about modeling a Ubiquitous (= überall vertreten) Language in an Bounded Context. | |
| It avoids the design of monolithic applications. | |
| Use DDD when the business model complexity is high (higher than the technical aspects of the project). | |
| Bounded Context - semantic contextual boundary | |
| Within the boundary, each component of the software model has a specific meaning and does specific things | |
| The components inside a Bounded Context are context specific and semantically motivated. | |
| In the Beginning of software modeling the Bounded Context is only coceptual and is part of the Problem Space. |
| class Invoice { | |
| ... | |
| @beforeMethod(Validators.customValidate) | |
| @afterMethod(Serialize) | |
| @afterMethod(AsyncAdvices.postResult, 'url..') | |
| @afterMethod(triggerUpdates) | |
| doCheckout(shippingDetails){ | |
| this.shippingDetails = shippingDetails | |
| } | |
| ... |