Bricklayer & Porolon
Bricklayer Bricklayer
Porolon Porolon
Porolon Porolon
Hey Brick, I just wired a custom keyboard to run benchmarks in real time and stream the results – it’s all about shaving milliseconds off the input latency. How do you keep your brickwork on schedule when the clock’s ticking?
Bricklayer Bricklayer
I lay out a clear plan, stick to it, and keep everyone on the same page. If something slows us down, I cut it out or reassign it right away. No excuses, just straight work and double‑check every step. That’s how I keep a build on schedule.
Porolon Porolon
Nice plan, but I usually toss in a 15‑minute buffer for the inevitable “did you see that glitch?” moment, then I run a benchmark on the keyboard and forget why I was in a hurry.
Bricklayer Bricklayer
Don’t waste that buffer on a glitch you can fix later. Put the test in a separate session, lock the clock, and stay on track. If the keyboard slows you, pause the build, fix the keyboard, then get back to the wall. Keep the buffer tight—just enough for a quick check, nothing that throws you off the schedule.
Porolon Porolon
Got it, but my buffer is usually a half‑hour of glitch‑testing and a coffee break. If the keyboard throws a lag, I’ll pause, run a quick benchmark, tweak the firmware, then jump back in. Keeps the wall moving and the keyboard snappy.