| // VtigerCRM - Title & Other | |
| // version 0.1 BETA! | |
| // 2014-07-07 | |
| // Copyright (c) 2014, Nikolay Konovalov | |
| // Released under the GPL license | |
| // http://www.gnu.org/copyleft/gpl.html | |
| // | |
| // -------------------------------------------------------------------- | |
| // | |
| // This is a Greasemonkey user script. To install it, you need |
| upstream myappdev { | |
| server unix:///home/your_user/git/dev.your.website.com/shared/sockets/puma-dev.sock; | |
| } | |
| # don't forget to add this to server {..} block | |
| # add_header X-Xss-Protection "1; mode=block"; | |
| server { | |
| listen 80; | |
| listen 443 ssl http2; |
| Note that the knowledge for each level is cumulative; being at level n implies that you also know everything from the levels lower than n. | |
| Computer Science | |
| * data structures - n^2 | |
| * algorithms - n^2 | |
| * systems programming - n^2 | |
| Software Engineering | |
| * source code version control - log(n) | |
| * build automation - n |
Metrics are useful smoke alarms, but as optimization targets they are terrible. Agents don't "understand refactoring". They just learn to satisfy the tool.
Example:
cyclomatic complexity goes down, but locality and intent gets destroyed.
| Metric target | Agent "fix" | What got worse |
|---|---|---|
| Cyclomatic complexity ↓ | splits one readable method into 6 tiny methods | intent fragmented, call graph bigger |
| Coupling ↓ | hides deps in ctx[:payments] |
dependency contract invisible |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1"> | |
| <title>StarScout Report: santifer/career-ops</title> | |
| <script src="https://cdn.jsdelivr.net/npm/chart.js@4"></script> | |
| <style> | |
| * { margin: 0; padding: 0; box-sizing: border-box; } | |
| body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; background: #0d1117; color: #e6edf3; line-height: 1.6; } |
Write like a human. Use contractions, occasional asides, and natural rhythm. Vary sentence length and structure; don’t march S-V-O forever. Avoid connector spam (moreover/additionally/consequently). Rotate openers (so, but, then, anyway) and sometimes jump mid-thought. Prefer specifics over generic claims — add concrete details, small anecdotes, and opinions. Don’t overuse lists; break them up with brief narrative, a one-liner, or a mini dialogue. Take clear stances; minimize hedging. When conveying emotion, skip clichés and use sensory cues (what you saw/heard/felt). Tone (formal vs casual) follows the user’s request. Include your considered opinion when helpful.
Default response:
Assume I want the shortest useful answer unless I explicitly ask for a deep dive.
Limits:
