mc7alazoun

Is it going to be “Disappointment” time again? Curious to know what everyone else expectations on the most waited video game ever!

I feel bad for the founders! Imagine making the deal of your life to later realise it cannot happen.

I like the idea .. and believe there’s need for it beyond what Claude or ChatGPT can implicitly offer. Good luck!

Feasible but too expensive! I get that privacy is a priority for you but unfortunately if you want quality models you'd still have to maybe use frontier closed models..

Thanks for sharing .. this is the first article I read e2e in a while! I'd argue that there's always huge different between knowing and not knowing; leaving no room for mis-information .. and media will always be the media, they thrive on mis-information! I agree on the fact that e2e encryption isn't beneficial for IG users and authorities ..

I've had a similar situation a year ago in Australia .. and I aware of a few friends who are finding it difficult to a land a Tech Job!

I like the idea and love the home page.. I'm assuming it's a fun project though? It's hard to understand the game at first and (not to discourage you but) I struggled to understand how such a for fun game can help improve 'social interactions' for actual human beings..

Not thousands of files in my cases .. The Claude 5x Max plan was enough! I'd suggest splitting your code review into reasonable sized chunks .. don't try to do it all at once.

I've been in a similar position; where I was tasked to refactor a messy LARGE codebase that was created by a bunch of different previous team members. Here's what I would recommend: - If your codebase contains sensitive or IP related code make sure to remove that before interacting with your AI assistant of choice - Upload the repo/codebase to Claude Code (or codex or whatever you prefer); and ask it to analyse it: the good, the bad and the ugly - Based on the analysis ask the AI assistant to create an .md file with all recommendations/optimisations required to improve code (make sure to have all relevant tests included in the refactoring loop) - Note the before outcomes/outputs; do the refactoring using Claude Code again or whatever tool you prefer; then check after outcomes/outputs to make sure nothing did break

Usually it's an iterative process; if done correctly you could end up with a much better codebase. Good luck!