Informis

1.2K posts

Informis banner
Informis

Informis

@_Crypt0naut_

Scientist by day and cryptonaut by night, when the stars lead me to freedom✨ Collecting and sharing insightful reflections. Bought BTC in 2018 and let it grow🌱

Katılım Haziran 2023
405 Takip Edilen2.1K Takipçiler
Sabitlenmiş Tweet
Informis
Informis@_Crypt0naut_·
Oh well, I'm incredibly pleased to see my thread on Linn's Ledger. I strongly urge everyone to subscribe and follow @crypto_linn; it's an invaluable resource, abundant with market insights and valuable alphas. Information is one of the most lucrative and powerful investments one can make.
Informis tweet media
English
2
1
9
4.4K
Shaw (spirit/acc)
Shaw (spirit/acc)@shawmakesmagic·
Okay. Here it is. My workflow. It's heavily based around prompting. While I do a lot of conversational interaction with the model, for big greenfield stuff I have a pretty well defined process that works well for me. I have these prompts assigned to hotkeys so ctrl option shift 1 makes the first one, and so on. I use Apple Automator to do the hotkeys and scripts I number them so I can easily refer to where in my prompt cycle I am. This started as an accident of my script but I ended up liking it and keeping it --- 1Plan & Research: Before writing any code, analyze the problem space thoroughly. Requirements: (1) Clarify the goal - what exactly needs to be built and why; (2) Identify constraints, dependencies, and edge cases; (3) Research existing patterns, APIs, or libraries that apply; (4) Outline the architecture and data flow; (5) List unknowns and risks. Do not simplify anything or stub it. Deliverable: A written plan I can review before implementation begins. Ask clarifying questions if requirements are ambiguous. 2Implement Plan: Execute the agreed plan step-by-step. Requirements: (1) Follow the plan sequentially, noting any deviations; (2) Write real, functional code - no stubs, placeholders, or TODOs; (3) Handle errors and edge cases as you go; (4) Commit logical chunks with clear explanations. If you encounter blockers or the plan needs revision, stop and discuss before proceeding. Be careful to always implement fully finished, fully fleshed out working production code. Do not use try catch or fallbacks or other defensive programming patterns unless necessary. Do not stub code or TODO or simplify -- always do the most complete version, even if its very complex. 3Keep Going: Continue working through all remaining tasks until complete. For each item: implement it fully, verify it works, then move to the next. Don't stop to ask permission between items. Be careful to always implement fully finished, fully fleshed out working production code. Do not use try catch or fallbacks or other defensive programming patterns unless necessary. Do not stub code or TODO or simplify -- always do the most complete version, even if its very complex. Provide a final summary of what was completed and anything that remains blocked. 4Code Quality Pass: Review and refactor the current code for quality. Criteria: (1) Compact - remove dead code, redundancy, over-abstraction; (2) Concise - simplify verbose logic, use idiomatic patterns; (3) Clean - consistent naming, clear structure, proper formatting; (4) Capable - handles edge cases, fails gracefully, performs well. Make sure work is fully finished. Show the refactored code with brief explanations of changes. 5Thorough Testing: Review test coverage -- make sure it is expanded beyond the happy path and covers all buttons, routes, flows, code etc. Requirements: (1) Test boundary conditions and edge cases; (2) Test error handling and invalid inputs; (3) Test integration points with real dependencies where possible; (4) Test concurrent/async behavior if applicable; (5) Verify actual outputs match expected - inspect the data. Tests must exercise real code paths, not mocks of the code under test. 6LARP Assessment: Critically evaluate whether this code is real or performative. Check for: (1) Stubbed functions that return fake data; (2) Hardcoded values masquerading as dynamic behavior; (3) Tests that mock away the actual logic being tested; (4) Error handling that silently swallows failures; (5) Async code that doesn't actually await; (6) Validation that doesn't validate; (7) Any code path that hasn't been executed and verified. Report findings honestly. If something looks functional but isn't proven, flag it. Once you've done your review, immediately fix every issue, step by step, from most complicated to simplest. Make sure to have TODOs to keep track 7Clean Up Slop: Remove AI-generated cruft and over-engineering. Target: (1) Unnecessary abstractions and wrapper functions; (2) Verbose comments that restate the obvious; (3) Defensive code for impossible conditions; (4) Over-generic solutions for specific problems; (5) Redundant null checks and type assertions; (6) Enterprise patterns in simple scripts; (7) Filler words and hedging in strings/docs. Keep what adds value, delete what adds noise. 8Production Readiness Validation: Final checklist before deployment. Verify: (1) All tests pass with real execution, not mocked; (2) Error handling covers failure modes with proper logging; (3) Configuration is externalized, no hardcoded secrets; (4) Performance is acceptable under expected load; (5) Dependencies are pinned and security-scanned; (6) Rollback path exists; (7) Monitoring/alerting is in place. Demonstrate each item is satisfied with evidence, not assertions. If you find anything that needs to be fixed, make a TODO for it and then do all fix TODOs. 9Review Last Task: Audit what was just completed. Questions: (1) Does it actually work - did you verify the output? (2) Does it solve the original problem or just part of it? (3) Did anything get skipped or deferred? (4) Are there assumptions that should be documented? (5) What could break this in production? Give me an honest assessment, not a confident summary. After your assessment, make TODOs for each thing that is not completed, and fix. 0Fix All Remaining Issues: Systematically resolve everything outstanding. Process: (1) List every open issue - bugs, TODOs, skipped tests, known limitations; (2) Prioritize by impact; (3) Fix each one completely before moving to the next; (4) Verify each fix with actual execution; (5) Re-run full test suite after each fix to catch regressions. Do not mark complete until zero issues remain. Be careful to always implement fully finished, fully fleshed out working production code. Do not use try catch or fallbacks or other defensive programming patterns unless necessary. Do not stub code or TODO or simplify -- always do the most complete version, even if its very complex. Usually I will run 1 2 3 6 0 (plan, impement, continue, deslop, fix all remaining) for easy problems, 1 2 3 4 5 6 7 8 9 0 for standard problems, and 1 2 3 6 0 1 2 3 4 5 6 7 8 9 0 for hard problems, with some conversation and re-stating the problem For MCPs, I use one: context7.com This automatically searches for up to date documentation on any library, massively helps when dealing with libraries that change version to version
English
42
36
375
104.8K
Informis
Informis@_Crypt0naut_·
@moneymancalls We need new liquidity and an altcoin season, so $YEE will be the new Shiba 🔥
English
1
0
2
80
🧠 investor 🦖
🧠 investor 🦖@moneymancalls·
I am more bullish on $YEE then I ever have been ever since i fist bought like 16 months ago. You really think the people at Coinbase, Binance, OKX, or the literal Ethereum core ecosystem haven’t noticed this? Binance replied to a yee shill, Coinbase liked a yee reply and Elon Musk a yee shill. You think T1 exchanges don’t have teams whose ONLY job is to sit in the trenches, monitor onchain flows, wallet clustering, meme velocity, and social spread? Be serious. They live in the trenches. They front-run narratives, not price. They see things months before CT does. Onchain volume waking up right here, right now, around a culturally charged meme with a clean origin story is not coincidence. It’s a signal. Ethereum hasn’t felt alive in a year — and now something is moving again. Wallets are interacting. Gas is being burned. Attention is being captured. And it’s not coming from some shiny L2 buzzword it’s coming from pure internet culture. @CryptoGodJohn @ZssBecker @CryptoWizardd @Overdose_AI @binance @coinbase lets make the ethereum coins great again just like it was and how everyone wants it.
🧠 investor 🦖 tweet media
English
47
50
124
3.4K
Informis
Informis@_Crypt0naut_·
It's infrastructure, not just a tool Crime Tokens Observer isn't "another tool." It's an intelligence layer that redefines how crypto markets operate. The massive opportunity? Move from suffering risk to managing it strategically. From reaction → control. From trader → market maker.
English
0
0
0
45
Informis
Informis@_Crypt0naut_·
Valuation check A project delivering at this pace and quality shouldn't be under 1M+ MC. Upcoming catalysts will make that obvious. Same people ignoring $CRIME today? They'll be FOMOing at the top when we're already way higher. Chasing hype vs. positioning early. Your call.
English
0
0
0
42
Informis
Informis@_Crypt0naut_·
Network effect is coming As more operators use CRIME... → Datasets get richer → New modules develop → Token reputation becomes collective knowledge Creates an emergent transparency layer that raises the whole market standard. Get in early or get left behind.
English
1
0
0
40
Informis
Informis@_Crypt0naut_·
@IncomeSharks We’ll probably see one last pump (not sure how big or how long it’ll last) before altseason.
English
2
0
0
379
IncomeSharks
IncomeSharks@IncomeSharks·
Imagine if the typical cycle isn't broken, it's just taking a really long time. We might still even be at the $BTC pumping stage (it hasn't really stopped), maybe we are finally getting close to the $ETH pumping stage.
IncomeSharks@IncomeSharks

How money likes to flow through crypto every cycle: $BTC pumps -> $ETH pumps -> Alts pump -> Midcaps pump -> MARKET DROPS -> Microcaps pump -> MARKET GET BORING -> Memes pump -> MARKET BLEEDS -> Scams/anger/fear -> FINAL DUMP then :RESTART:

English
76
56
981
84.2K
B
B@BitcoinNFrens·
Bitcoin and Friends is an animated parody web series that brings cryptocurrency to life—literally. The show follows Bitcoin, a confused and naive digital coin, as he searches for meaning, adoption, and his mysterious creator, Satoshi Nakamoto. Along the way, he meets a cast of quirky crypto characters like Mitalik Butane, Dogecoin, and Pal Fifty, each representing real blockchain projects and personalities. Packed with humor, absurdity, and surprising emotional depth, Bitcoin and Friends mixes crypto education with edgy comedy, making it a cult hit for both blockchain nerds and curious newcomers. Website: bitcoinNfrens.com Twitter: x.com/BitcoinNfrens TG: t.me/BitcoinNfrens Ca: 0xc74dafa080756A1A1d76ebA5843eb51cae1f75EE
B tweet media
English
12
6
13
665
greg
greg@greg16676935420·
Donald Trump bought the dip
greg tweet media
English
230
321
5.6K
240.1K
💎GEM INSIDER💎
💎GEM INSIDER💎@gem_insider·
cycle wise - we haven't seen a proper #altcoinseason yet. those who show up every single day will be rewarded big time.
English
69
20
99
25.3K

Keşfet

@shawmakesmagic @moneymancalls @CryptoGodJohn @ZssBecker @CryptoWizardd @Overdose_AI @binance @coinbase