Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I switched VS Code theme to light to avoid attracting attention (as most of our screens are mostly white normally) when using it occasionally while my job had nothing to do with VS Code (or any code at all). Everyone procrastinates. I wrote some code for sake of procrastination, instead of using social networks like normal people do. Some may probably call this "ill-intent".



Sounds like a bad idea. While stealthier in your case, writing code with a light color theme is heresy. :)


ADHD: I actually feel more focused with the light theme, dark theme somehow feels overwhelming.

OCD: The idea of having some apps dark and some light (some apps, let alone websites don't support dark themes) feels horrible.

Sun: shining bright from the back, straight into my monitor, good luck reading anything with a dark theme.


If I'm honest, I very likely have un-diagnosed ADHD or am on the spectrum at some level. I'm most assuredly OCD. I often have an easy time getting my own office over other techs because I'm willing to sit in what amounts to a broom closet with no windows to escape the nasty, overhead fluorescent lighting prevalent in most office settings. My username should give a hint. I love overcast skies, dark offices, and dark terminal windows and IDEs. Strangely enough, I cannot stand dark theme browsers setups. Surfing the web with a dark theme seems almost like wading through fog.


Might be because dark browser themes are rarely complete enough. There's always something off; last time I tried to theme a fully dark Firefox, I couldn't get the address bar text to be light with a dark background.


Everything you describe is the same for me.


All of that being said, it's still heresy. Just because it may be "right" doesn't mean it's not heresy. Ask history.


If dark theme zealots spent less time evangelising, maybe their eyes wouldn't hurt so much.


Sounds like a bad idea. While I don't agree with the job agreements that claim any work you do on your personal computer outside of work hours belongs to the company, it would be hard to claim such code should not belong to the company if you do it during work hours.


You don't have to claim the code if nobody knows it exists in the first place. It was not anything I ever meant to show anybody. Just small utilities for myself, meant to actually improve my productivity.


Long ago I had a college job doing data entry for a tiny long-distance carrier. We had hourly quotas, etc. and had to retype the information into several different backend systems. One day I dug up a manual and discovered that there were a copy/paste commands available on the terminal we were using. I could get through my quota in 40 minutes. I showed this to my supervisor who told me “we’re paying you to type not to play around on computers”. For the rest of the summer I took a nice long coffee break every hour.


I was once a temp worker hired to transfer a bunch of records from an old, terminal-based mainframe into a newer Windows-based app for an insurance company. I spent about an hour doing so and then went and asked the supervisor if their IT department had an old copy of Windows 3.11 lying around (this was Win 98). 3.x had the "macro recorder" that would capture everything - including mouse movement. They did.

I practiced highlighting all the fields, switching apps, and pasting the data. You could only play back at maybe 3x original speed. Then I started my macro running. I had estimated that I could have done it manually in about three days; the macro would do it in about 30 hours and not screw up any of the data along the way. Told the supervisor what I'd done and asked to be paid for two. She said yes and offered me a job on the spot; too bad I was starting med school in a month.


In highschool math, we were learning LRAM, RRAM, and MRAM - where you estimate the "area under a curve" by making rectangles and then summing their area. A very interesting technique but very manual to calculate.

I wrote a program from scratch on my TI-82 to calculate the answers and my math teacher said "You wrote the program yourself, so you can use it during the exams. You still have to show your work manually, but it sounds great to check your work."

This was a pivotal moment in my path to becoming a software engineer. :)


Ditto. During my college internship (1999), I worked the night shift for a certain very large OG domain name registrar. We had a nightly quota of about 200 domain names to take from being registered to the vanilla configuration. Since this was a Unix environment and I was actually learning shell scripting in college at the time, this was the perfect opportunity to script. I received permission from the greybeard running the servers to proceed with the caveat he vetted the code before making it executable. I went from taking almost 5-6 hours to doing my quota in mere minutes. My boss learned of this and told me to keep it a secret from the other techs. He then put me to work writing code to paginate reports and other things. On my last day at the job, I shared the code with everyone.


The second part of that sentence, probably omitted by your boss “… play with computers. The same way we are charging our client for a highly unoptimised process where we charge by person/hour, don’t make it look like it can be done more efficiently or I’ll fire you”


you're lucky he/she didn't kick you out; go and justify "I need 12 people to do something that one person can do in 1 day, alone"




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: