dmj.one

Work / Tools / Universal Bootstrap

A new way to start.

Click. Wait. Code.

A fresh Windows machine, turned into a professional engineering station, in the time it takes to make a coffee. One double-click. Java, Python, C, C++, MySQL, VS Code and Git, all set up at the same time.

View source How it works
Built by Nikhil Bhardwaj · Under dmj.one
1Double-click to start
7Tools installed together
3 stepsDownload · Extract · Launch
0 PATHManual config needed
d1runUnified execution engine

Act I · The Problem

A blank Windows install is a two-day fight.

Mismatched JDKs. PATH variables that argue with each other. A C++ program that compiles in the morning and refuses to link by lunch. A first-year student who wanted to write code, who is now reading a Stack Overflow thread from 2014 about MinGW. The fight kills the curiosity before the code even starts.

Act II · What Is Inside

Seven tools.
One install.

Industry standards, picked once, configured well, kept current. No bring-your-own. No "now download MinGW separately". Everything the first month of an engineering degree needs, sitting in one folder.

Lang Java OpenJDK · LTS
Lang Python PATH-managed
Lang C / C++ MinGW · static
DB MySQL Native service
IDE VS Code Tuned defaults
VCS Git Ready to clone

Act III · The Lifecycle

Five quiet moves.
Nothing for you to babysit.

An orchestration engine, not a script. It looks at the machine, decides what is missing, fetches it, configures it, brings the database service up, and then proves it works before stepping aside.

  1. 01 · Detect

    Read the machine.

    What is already installed. What versions. What conflicts. The script branches, instead of stomping over a working setup.

  2. 02 · Download

    Pull the right builds.

    Vendor sources, correct architecture, current LTS. Resumes on flaky networks. Hashes verified.

  3. 03 · Install

    Quiet, in order.

    Java first, then compilers, then Python, then MySQL as a native Windows service. Then the editor on top.

  4. 04 · Configure

    PATH, env, MySQL boot.

    System PATH set once and well. MySQL service registered to start at boot. VS Code opened on a sane workspace.

  5. 05 · Validate

    Prove it before you exit.

    A compile, a run, a database connection. If anything failed, you know now, not on day three.

One more thing.

We reinvented how you run code.

Running a C++ program with a MySQL connection used to mean fighting the linker. Running Java meant minding the classpath. We built d1run: one command, every language, the right flags chosen for you.

d1run main.cpp

compiles, links MySQL, runs the binary, prints the output.

d1run app.py

picks the right Python, runs the script, no virtualenv dance.

d1run Project.java

compiles, sets the classpath, runs the main class.

d1run mvn / gradle

auto-detects Maven and Gradle projects, runs the right build.

Act IV · The Safety Net

An auto-push monitor in the background.

If you write a meaningful amount of code, the monitor turns on a failsafe and quietly pushes your work to the cloud. Curiosity should not punish a student because their laptop dies at 11 p.m.

Watcher

Sees your workspace, not your files.

Counts code volume. When you cross a threshold the failsafe arms. Inactive otherwise. No telemetry leaves the machine until you commit.

Tester

Built-in fuzzing and stress.

A small testing suite ships with the bootstrap, ready to throw weird inputs at student code so failures show up on a workstation, not in a grading session.

The Stack

Boring underneath. Effortless on top.

  • OpenJDK · LTS
  • Python (PATH-managed)
  • MinGW · C / C++
  • MySQL · native service
  • VS Code
  • Git
  • d1run · execution engine
  • Maven · Gradle detect
  • Auto-push monitor
  • Windows · start.bat

If a first-year student can ship a working dev box in one click, so can your onboarding.

The dmj.one welfare initiative builds tools that put complete environments in the hands of people who do not own the words for "PATH variable" yet. Bring us in to do the same for your team.

Hire me Back to work