A minimal multi-agent system with an orchestrator, a planner, a coder, and a designer working together providing orchestration between Claude, Codex and Gemini.
Install all agents listed below into VS Code Insiders...
| Title | Type | Description |
|---|
hi, i'm daniel. i'm a 16-year-old high school senior. in my free time, i hack billion dollar companies and build cool stuff.
about a month ago, a couple of friends and I found serious critical vulnerabilities on Mintlify, an AI documentation platform used by some of the top companies in the world.
i found a critical cross-site scripting vulnerability that, if abused, would let an attacker to inject malicious scripts into the documentation of numerous companies and steal credentials from users with a single link open.
(go read my friends' writeups (after this one))
how to hack discord, vercel, and more with one easy trick (eva)
Redacted by Counsel: A supply chain postmortem (MDL)
| import { Injectable, Renderer2, Inject, RendererFactory2 } from '@angular/core'; | |
| import { DOCUMENT } from '@angular/common'; | |
| import { RuntimeConfigLoaderService } from 'runtime-config-loader'; | |
| import { Router, RouterEvent, NavigationEnd } from '@angular/router'; | |
| import { filter, tap } from 'rxjs/operators'; | |
| declare let gtag: Function; | |
| @Injectable({ | |
| providedIn: 'root', |
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.
| @NgModule({ | |
| imports: [OAuthModule.forRoot({...})] // <-- how to use the configuration.json here | |
| }) | |
| export class AppModule { | |
| constructor(@Inject(AppConfig) private readonly appConfig: AppConfiguration) {} // I can inject | |
| } |
| import { ComponentFactoryResolver, ComponentRef, Directive, EventEmitter, Input, Type, ViewContainerRef } from '@angular/core'; | |
| import { Subscription } from 'rxjs'; | |
| @Directive({ | |
| selector: '[lazyComp]' | |
| }) | |
| export class LazyCompDirective { | |
| private _inputs; | |
| private _outputs; | |
| private subscription = new Subscription(); |
| import {AbstractControl, FormArray, FormControl, FormGroup, ValidationErrors} from '@angular/forms'; | |
| import {Injectable} from '@angular/core'; | |
| import {debounceTime, distinctUntilChanged} from 'rxjs/operators'; | |
| export declare interface ServerError { | |
| [key: string]: []; | |
| } | |
any: magic, ill-behaved type that acts like a combination of never (the proper [bottom type]) and unknown (the proper [top type])
never is assignable to any, and any is assignable to anything at all.any & AnyTypeExpression = any, any | AnyTypeExpression = anyunknown: proper, well-behaved [top type]
unknown. unknown is only assignable to itself (unknown) and any.unknown & AnyTypeExpression = AnyTypeExpression, unknown | AnyTypeExpression = unknownany whenever possible. Anywhere in well-typed code you're tempted to use any, you probably want unknown.| import { | |
| Compiler, | |
| ComponentRef, | |
| Directive, | |
| Inject, | |
| Injector, | |
| Input, | |
| NgModuleFactory, | |
| OnInit, | |
| Type, |