Live data from Hacker News

"We ran out of columns"

jimmyhmiller.github.io

161–170 of 588 posts

Re: "We ran out of columns"

#161
post #157

Earlier quoted context omitted.

I was one of those once. Tried to get CVS in a project. Then some other dev committed 9MB of tabs 0x09 at the end of a file. Then the site was "slow" (cause the homepage was 10MB). And the blame went to...CVS somehow. I left.

Then they probably fired the guy who deleted 2MM lines of tabs for not meeting LoC metrics.

Many years later there was a scene in Silicon Valley where their VC set a tequila bottle on the delete key and caused havoc.

That's when I figured out what happened in 1998.

Re: "We ran out of columns"

#162
post #69

Earlier quoted context omitted.

Visual SourceSafe would show that a file was checked out hinting to maybe stay away. Good times.

We still use VSS for a couple codebases. We’re a small enough team that conflicts are rare, but the occasional Teams message “hey, let me know when you’re done with module.cpp” is not unheard of.

I’m impressed VSS still works. I used it as part of my first professional software engineering job in 2008 and it felt old then.

Re: "We ran out of columns"

#163
post #77

Probably some of the worst code I ever worked on was a 12k+ line single file Perl script for dealing with Human Genome Project data, at Bristol-Myers Squibb, in the late 1990s. The primary author of it didn't know about arrays. I'm not sure if he didn't know about them being something that had already been invented, or whether he just didn't know Perl supported them, but either way, he reimplemented them himself on t…

> and it still passed all the tests

All his sins can be forgiven because he made it so easy to refactor by writing comprehensive tests.

Re: "We ran out of columns"

#164
post #69

Earlier quoted context omitted.

Visual SourceSafe would show that a file was checked out hinting to maybe stay away. Good times.

We still use VSS for a couple codebases. We’re a small enough team that conflicts are rare, but the occasional Teams message “hey, let me know when you’re done with module.cpp” is not unheard of.

Fascinating. An anachronism worthy of steampunk novels!

Re: "We ran out of columns"

#165
When it comes to building things, the outcome is dictated by the constraints. But not the way most people realize.

Constraints affect outcomes in (at least) three ways:

  - by absolute limitation (you cannot violate these)
  - by path of least resistance (the constraint makes X easier)
  - by strategy (creative use of knowledge & skills leads to novel solutions)
---

There is an injured person on top of a mountain, and they need medical attention. You need to go up the mountain, get them, and bring them down.

You only have so much strength/endurance, so nothing you do will ever be faster than what your body is capable of. You need to get up and down in less than two hours. You need to carry an injured person. The mountain has two slopes: a long gradual one, and a short steep one.

Most people would climb the long gradual slope, because it's the path of least resistance. But it will take 4x as long to climb up and down it. Climbing straight up the steep slope would be incredibly tiring, and unsafe to bring someone down.

You can, however, zig-zag up and down the steep hill. It will take more time than going straight up, but faster than the long way, you will be less tired, and it's safer to bring someone down hill.

---

Constraints can be good and bad. Good use of constraints can allow you to get something done effectively. Bad use of constraints leads to failure. So it's important to have someone who can utilize those constraints effectively.

Vision, leadership, and wisdom is more important than the people, skills, materials, or time involved. The former determines the quality of the outcome more than the latter.

Re: "We ran out of columns"

#166

Earlier quoted context omitted.

This is amazing. I can so well imagine a bright young hire joining that team, helpfully offering to "setup this thing called git" only to be laughed out of the meeting by all the "senior" staff.

I've been that person a few times. 1. The only developer on the team with Github and put forward the idea of the company not hosting their own source code with TFS. 2. The only developer using branches with git when the co-founder asked (demanded) everyone to only use master. The list goes on!

Here’s a few of my horror stories where I was a consultant at various companies:

1. Previous consultants left no documentation or anything, and a running Hadoop cluster handling (live!) 300 credit card transactions a second. Management hired 8 junior sysadmins - who were all windows sysadmins, had never used Linux before, and were expected to take over running this Linux cluster immediately. They all looked at me white as ghosts when I brought up SSH prompt, that’s the point where I learned they were all windows sysadmins.

2. Another company: all Java and MySQL developers who were trying to use Spark on Hadoop, refusing to learn anything new they ended up coding a Java app that sat on a single node, with a mysql database on the same node, that “shelled out” to a single trivial hello-world type function running in spark, then did the rest of the computation in Java on the single node, management celebrated a huge success of their team now using “modern cluster computing” even though the 20 node cluster did basically nothing and was 99.99% idle. (And burning huge $ a month)

3. Another company: setup a cluster then was so desperate to use the cluster for everything installed monitoring on the cluster, so when the cluster went down, monitoring and all observability went down too

4. A Cassandra cluster run by junior sys-admins and queried by junior data scientists had this funny arms race where the data scientists did what was effectively “select * from *” for every query and the sysadmins noticing the cluster was slow, kept adding more nodes, rather than talk to each other things just oscillated back and forwards with costs spiralling out of control as more and more nodes were deployed

Any many more!

This might sound like I’m ragging on juniors a bit but that’s definitely not the case - most of these problems were caused by bad management being cheap and throwing these poor kids into the deep end with no guidance. I did my best to upskill them rapidly and I’m still friends with many of them today, even though it’s nearly 10 years later now,

Good times!

Re: "We ran out of columns"

#167

Earlier quoted context omitted.

This is amazing. I can so well imagine a bright young hire joining that team, helpfully offering to "setup this thing called git" only to be laughed out of the meeting by all the "senior" staff.

I started in 2008. This is what I did eventually. Over the years I introduced the small company to Linux, git, defensive programming, linting, continuous integration, Scrum..., but only for the new projects and stayed 13 years there. That old project though was never fixed though, probably still running that way now.

Same story here. Introduced static Python to our team’s entire codebase. Best place I’ve ever worked.

Re: "We ran out of columns"

#168

When I started at my first company, they had a very complex VB application running on dozens of customers around the country, each having some particular needs of course. There was a LOT of global variables (seemingly random 4 uppercase letters) controlling everything. At some point, the application had some bugs which were not appearing when the application was run in debug mode in Visual Studio. The solution was ob…

[deleted]

Re: "We ran out of columns"

#169
post #162
post #69

Earlier quoted context omitted.

We still use VSS for a couple codebases. We’re a small enough team that conflicts are rare, but the occasional Teams message “hey, let me know when you’re done with module.cpp” is not unheard of.

I’m impressed VSS still works. I used it as part of my first professional software engineering job in 2008 and it felt old then.

I'm so sorry. We were using it in the late 90s, and on a monthly basis it would be down for a day or two while the admin plunged out the database. Good times.

Re: "We ran out of columns"

#170

Earlier quoted context omitted.

This is amazing. I can so well imagine a bright young hire joining that team, helpfully offering to "setup this thing called git" only to be laughed out of the meeting by all the "senior" staff.

At this level of dysfunction, installing git won't do anything. You need a holistic change in thinking which starts with convincing people there's a problem.

I’ve yet to see people actually change their mind at this level. Firing is often the only way.
Post reply on HN