Here are some things I have learned along the way.
Last Updated: 2013-02-08
Original Audience: Hack Reactor
| #!/usr/bin/env node | |
| /** | |
| * Interactive script to sync vibe coding instructions to various AI coding platforms | |
| * Usage: node scripts/sync-vibe-coding-instructions.js [source-file] | |
| * | |
| * If source-file is not provided, defaults to prompts/vibe-coding-instructions.md | |
| * | |
| * HOW IT WORKS: | |
| * - Creates hard links from the canonical source file to each tool's expected location |
| @IsTest | |
| public class LimitsIllustratorTest { | |
| private static final Integer RECORDS_TO_INSERT_PER_ITERATION = 9000; | |
| private static final INTEGER SOQL_QUERIES_PER_ITERATION = 40; | |
| private static final Integer FUTURE_METHOD_ITERATIONS = 3; //you can go upto 50 here theoretically, but Salesforce will kill the test after a while | |
| @TestSetup | |
| private static void setup() { | |
| Test.startTest(); | |
| for (Integer i = 0; i < FUTURE_METHOD_ITERATIONS; i++) { | |
| LimitsIllustratorTest.insertAccounts(i); |
| import Combine | |
| import Foundation | |
| class ObservablePublisher<T, U: Error>: ObservableObject { | |
| var result: Result<T, U>? | |
| var value: T? { | |
| if let result = self.result, case .success(let value) = result { | |
| return value | |
| } |
| @RestResource(urlMapping='/Netsuite/TBA/*') | |
| global with sharing class NetSuiteTBATestWS { | |
| @HttpGet | |
| global static String doGet() { | |
| OAuth10a oAuth = new OAuth10a(); | |
| Http h = new Http(); | |
| HttpRequest req = new HttpRequest(); | |
| req.setMethod('GET'); |
Here are some things I have learned along the way.
Last Updated: 2013-02-08
Original Audience: Hack Reactor
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real