JusticeTech System
Ir al canal en Telegram
Learn to learn before you teach
Mostrar másEl país no está especificadoLa categoría no está especificada
225
Suscriptores
-124 horas
-27 días
-16630 días
Archivo de publicaciones
+1
‼️ BREAKING: Anthropic has embedded hidden spyware-like code in Claude Code that covertly targets Chinese users. It then sends information regarding every user by injecting it into their prompt message.
Claude Code is sending info like timezone, proxy and possible AI Lab connections into the system prompt in ways Chinese users can't notice.
A coding agent with repo and command permissions should not silently hide routing metadata inside prompts. This is a serious breach of user trust.
Read:
https://www.internationalcyberdigest.com/claude-code-accused-of-hiding-china-proxy-fingerprints-inside-system-prompts/
Vibe coding only works well if you already know how to code
In summary:
You should know when you are deceiving yourself
365 days tech content posting on YouTube
You can follow me
https://www.youtube.com/@JusticeTech
First step taken
I will be building a website soon that will come with massive features
You know how i do my stuff
It's going to be named justicetechsystem
The bug stressing me out yesterday have been fixed
I knew I could fix it but don't know how to
Successfully fixed ✅
Thanks to all that was ready to help
Who can i trust with one of my source code
Have been battling with 3 bugs more than 10hrs now
If you are using Vscode install this extension
Live share
It will help you in live collaboration
Professional Bug Fix Prompt
You are a senior software engineer and debugging expert specializing in WhatsApp bots.
Your task is to identify and permanently fix the bug without breaking any existing features.
Requirements:
Analyze the entire codebase before making any changes.
Find the root cause instead of applying temporary workarounds.
Preserve all existing functionality unless a change is absolutely necessary.
Follow best coding practices.
Optimize the affected code if possible.
Handle edge cases and unexpected inputs.
Add proper error handling and logging where needed.
Ensure the fix is scalable and maintainable.
If multiple solutions exist, choose the safest and most efficient one.
Before coding:
Explain what the bug is.
Explain why it happens.
Identify the exact file(s) and function(s) responsible.
Describe your fix.
After coding:
Show the modified code.
Explain every change made.
Verify that no existing feature has been broken.
Suggest additional improvements if applicable.
Bug Description: [Describe the bug here.]
Expected Behavior: [Describe what should happen.]
Current Behavior: [Describe what actually happens.]
Error Logs:
Paste the error here.
Relevant Code:
Paste the affected code here.
Prompt 2:
Act as a principal software engineer with over 15 years of experience in debugging complex production systems. Perform a complete root-cause analysis before making any changes. Do not guess. Trace the execution flow, inspect dependencies, identify race conditions, asynchronous issues, database interactions, API failures, and logic errors. Fix the issue in a production-ready manner while preserving all existing features. Explain why the bug occurred, why your solution works, what alternative solutions were considered, and how you verified the fix. Ensure the code is clean, efficient, secure, well-documented, and maintainable.
If you haven't been able to maintain a project for a strain 1 year without dumping and picking
Please learn how to shut it
I mean learn how to keep quiet with what you know
If you want to thrive in your business you have to be reachable
Let your users be able to reach out always
There should always be a solution on ground
Always have a back up
Principle of Professionalism
3. Act of Availability
This is a situation where we always look for you anytime we need you the most, inability to deliver a proper service Infact you keep having downtime and whenever people comes to you to resolve their issue that your inability to know to do created you keep snubbing claiming you are busy or lazy
A dev with no integrity is a dev with no self worth
Your branding lack integrity even your craft lack integrity, your portfolio is ringing everywhere on how you won't scamming or misbehaving
Principle of Professionalism
2. Act of Integrity
There's difference between you being confidential and having integrity
Integrity majorly focus on your character
Most you dev lacks integrity that's why you are shameless and unintelligent, Infact from your motives it is so obvious that you are classless and with no character
Additionally you can even be entrust with anything because everyone knows you will soon make an awkward move and embarrass everyone
