Most developers don’t control their environment
Most developers don’t configure their environment.
They install extensions.
They stack tools.
They let everything run automatically.
And over time, they lose control.
The problem is not formatting
It’s uncontrolled automation.
- format on save
- hidden transformations
- conflicting extensions
- inconsistent results between machines
What starts as “productivity” becomes:
→ unpredictable diffs
→ broken formatting
→ code that changes without you asking
The real issue: loss of control
When your editor modifies your code automatically, you are no longer in control of:
- when changes happen
- what changes are applied
- how your code is structured
That’s not tooling.
That’s delegation.
I built a different approach
Instead of automating everything blindly, I built a VS Code environment based on one idea:
Nothing happens unless you decide it.
No format on save.
No hidden actions.
No external dependencies.
Only explicit, controlled operations.
What this environment does differently
- No automatic formatting
- No “magic” behavior
- No dependency on extensions
Everything is:
- manual
- predictable
- reproducible
Controlled formatting, not automation
Formatting and cleanup are still there.
But they are:
- triggered manually via tasks
- applied only when needed
- executed locally with Python scripts
You decide:
- when to clean
- what to modify
- how far it goes
Local scripts, full control
Instead of relying on extensions:
-
clean.py→ removes useless spaces, fixes structure -
convert.py→ normalizes line endings -
space.py→ detects issues without modifying -
backup.py→ creates timestamped local backups
Everything runs locally.
No network. No hidden logic. No surprises. :contentReference[oaicite:0]{index=0}
Three execution modes
You can run actions:
- on the whole project
- on the active file
- on a custom selection
This avoids accidental global changes.
And keeps your code stable. :contentReference[oaicite:1]{index=1}
Why this matters
Because code is not just written.
It is maintained.
And maintenance requires:
- consistency
- predictability
- control
Blind automation breaks all three.
This is not about tools
It’s about responsibility.
If your environment modifies your code without you noticing:
You are no longer responsible for your code.
Your tools are.
Who this is for
- developers tired of fighting their editor
- teams needing consistent formatting
- anyone who wants a stable, predictable workflow
Final thought
Faster doesn’t mean better.
Automated doesn’t mean controlled.
And in the long run:
the code you control will always outlive the tools you depend on.
If you're interested in how it works under the hood:
Here’s a technical breakdown of the system architecture.
VS Code – Environment Pack
A configured working environment for Visual Studio Code.
This pack provides a clear and consistent framework for formatting, cleanup, and normalization
of common file types (.py, .html, .css, .js, .json, .txt),
using VS Code settings and locally executed Python scripts.
The goal is not blind automation,
but a controlled set of tools
that lets you keep full control over code structure, readability, and consistency,
regardless of the operating system.
Why this environment exists
Most editors automatically reformat code when saving files.
While convenient, this can introduce unexpected changes,
inconsistent formatting, or conflicts between extensions.
This pack takes the opposite approach:
- no automatic formatting
- no hidden actions
- manual tools executed only when needed
The goal is to keep code stable, readable and predictable,
while giving full control to the developer.
Pack Structure
vscode_environment_pack_v1.1/
│
├── .vscode/
│ ├── settings.json → Complete editor configuration (indentation, encoding, readability)
│ ├── keybindings.json → Custom keyboard shortcuts (navigation, editing)
│ ├── tasks.json → VS Code tasks for manual tool execution
│ ├── launch.json → Script execution within the environment
│ └── extensions.json → Local extension management
│
├── scripts/
│ ├── cleaning.py → File cleaning and normalization
│ ├── conversion.py → Format and encoding handling
│ ├── analysis.py → File analysis (read-only)
│ └── backup.py → Local file backup system
│
├── LICENSE.md → Terms of use and legal framework
│
└── docs/
├── TECHNICAL_README.md → Technical documentation and internal structure
├── README_COMMERCIAL.md → Project overview and public presentation
├── INSTALL.md → Installation and usage guide
│
└── examples/
├── before.py → Dirty / unstructured example files
├── after.py → Clean, formatted versions generated by the pack
├── convert_lf.mp4 → CRLF files automatically converted to LF
├── indent_clean.mp4 → Broken indentation/margins fixed instantly
├── indent_python.mp4 → Badly indented Python file auto-corrected
├── backup.mp4 → Demonstrates automatic file backup on each save (Ctrl + S)
│ and how to restore a deleted file from the backup folder
└── space_clean.mp4 → Broken file analyzed and margins detected (read-only)
If you want to explore the technical implementation, you can find it here:
https://github.com/Palks-Studio/vs-code-environment-pack
Top comments (0)