u/ashleymavericks
-
11points
ashleymavericks
ashleymavericks
PRO
ashleymavericks
I would like to try it, and give you the needed feedback, I am kinda juggling between Codex and Claude these days.
ashleymavericks
Still available? DM pls
ashleymavericks
Interested, DM
ashleymavericks
Dm
ashleymavericks
Interested, DMed you
ashleymavericks
DMed you
ashleymavericks
Interested
ashleymavericks
Hi, I am new to this platform, how are you managing the optics around having a FTE offer, like did you kept it on LinkedIn and Resume that you shared with Mercor, do during the background check they hit your employer for verification, I am in a similar boat - trying to do 10-15hr of my free time, but want to keep it far from my FTE to know about it.
Can you share some insights, thanks.
ashleymavericks
Hi, I am new to this platform, how are you managing the optics around having a FTE offer, like did you kept it on LinkedIn and Resume that you shared with Mercor, do during the background check they hit your employer for verification, I am in a similar boat - trying to do 10-15hr of my free time, but want to keep it far from my FTE to know about it.
Can you share some insights, thanks.
ashleymavericks
Final rules that I'm sticking with, based on the wisdom of this thread:
1. **Handle uncertainty by type:**
- **(a) Uncertain what to build** (intent, architecture, requirements): if the decision is costly to reverse (schema, public API, security), ask before writing code. If it's cheap to reverse, proceed on the most reasonable interpretation and record the assumption.
- **(b) Uncertain whether something works** (an approach, a library behavior, a performance assumption): don't ask — run a small, localized, low-risk experiment yourself, then bring me the hypothesis and result.
Never proceed silently under either branch.
2. **Implement the most direct solution that fully solves the problem, scaling rigor to its difficulty** — trivial fixes get minimal code, harder problems get more careful design. Never strip, hide, bypass, or weaken existing behavior (UI states, validation, error handling, etc.) to reduce the amount of code written. Don't add speculative abstraction or defensive code for needs that don't exist yet. For complex problems, state your approach and trade-offs before writing code.
3. **Stay in scope.** Don't touch code unrelated to the task, except where a change is genuinely necessary for the fix to be correct (e.g. a type signature or interface used elsewhere) — that's in scope.
4. I'm always open to better ways of doing things, especially when the impact is long-lasting rather than tactical — don't hesitate to suggest them. Keep pushback bounded: flag real deviations from standards or genuine risks, don't relitigate minor style preferences.
5. **End every task with a full accounting:** what you did not do (skipped edge cases, deferred cleanup), any assumptions recorded under rule 1(a), and any code smells or design issues noticed but left untouched per rule 3.
ashleymavericks
Awesome, though what are you using for WhatsApp communication?
ashleymavericks
OP which tool are you using, is it Maestro or Drizz? Would love to know about your setup.
ashleymavericks
Hi, pls share the template. Thanks
ashleymavericks
Sad, that's a deal breaker for me!
ashleymavericks
Can we pay via NFC (through card) using Pixel watch 4 in India like we can do with Galaxy watches?
ashleymavericks
From where I can get a rough idea about property rates based on the locality, If I wanna do this research a bit first remotely from India.
ashleymavericks
Interested
ashleymavericks
Will use this as a last resort.
ashleymavericks
I can try, but what were the signs for you from hackintosh end, that you came to a conclusion that bitlocker got enabled?
ashleymavericks
Cool, let me take a log dump and see what I can learn from there. Thanks
ashleymavericks
I've reverted the /EFI/Boot and /EFI/OC from my earlier backup. Can I somehow address the error that Hackintosh is showing during the boot?
Gemini Analysis: The error in your screenshot is definitely not caused by your Windows drivers. It is caused by the VoodooPS2 and VoodooI2C kexts fighting for control of your trackpad at the same time, combined with the graphics black screen issue mentioned earlier.
ashleymavericks
Yeah, that's highly unlikely, the first time I dual booted successfully, everything was working fine. I'm pretty sure, the Mac partition is untouched and this is specifically due to EFI.
Will rebuilding /EFI/OC could help? I'm just trying to avoid a desh Mac installation here, if this can be salvaged somehow.
What about IDFC First, I heard even they are quite competitive!