It’s a Unix system I know this
61–64 of 64 posts
Re: It’s a Unix system I know this
#62> Surely, “just whip up a solution in an hour” doesn’t ever happen in reality. > > Right? Err, maybe the author hadn't experienced that before, but IMO that happens pretty frequently, even for projects that have been in production for years.
I've definitely experienced this before! But, like, its dramatically different if you're physically in the space and there's visible pressure. Its not like I was at home dealing with a crisis where I could more easily block out everything. And coding from scratch is significantly more stressful, imo, than bug fixing. In addition to my (former) day job, one of my side projects is a live service with ~60k monthly users…
For sure. Not dismissing the author’s achievement here, just noting that it does happen frequently in our industry.
P.S: I once had to fix something in prod during a demo of upcoming features to paying customers. Nothing like using Remote Desktop (yep not even SSH) into four servers to manually change a line in a bundled and minimised Nodejs app!
Re: It’s a Unix system I know this
#63Earlier quoted context omitted.
I've definitely experienced this before! But, like, its dramatically different if you're physically in the space and there's visible pressure. Its not like I was at home dealing with a crisis where I could more easily block out everything. And coding from scratch is significantly more stressful, imo, than bug fixing. In addition to my (former) day job, one of my side projects is a live service with ~60k monthly users…
> But, like, its dramatically different if you're physically in the space and there's visible pressure For sure. Not dismissing the author’s achievement here, just noting that it does happen frequently in our industry. P.S: I once had to fix something in prod during a demo of upcoming features to paying customers. Nothing like using Remote Desktop (yep not even SSH) into four servers to manually change a line in a bu…
Re: It’s a Unix system I know this
#64Earlier quoted context omitted.
Fair point, but sometimes, especially with a deadline and a rough idea of how you're going to implement something, it's faster to code something yourself, warts and all, rather than sifting through Github to find ones that look good, cloning, installing dependencies, and checking that they have all the features you need, they work correctly, and that you won't need to familiarise yourself with someone else's codebase…
Well, when I faced a similar problem (organizing large table tennis tournaments) which exceeded the limit of the usual free android apps (max 10 players), I prepared beforehand these two apps. And in one cases I even needed it then, because too many players showed up. Using a lame closed-source app causes always sweat, so I'm better well prepared. https://github.com/search?q=swiss+tournament&type=repositori... => 667…
You were able to find one that looks like the format she needed, but what would you have done if it doesn't? Or if it's broken?
It takes time to review > 300 lines of code, and she was on the clock. Even if she is able to read 1 line per second, it would take her five minutes just to read through the code, without downloading it, running it, testing it.
I absolutely agree that there should be a review of the contingency planning, but having more confidence in your coding abilities than your ability to search Github effectively is not necessarily wrong.