logoalt Hacker News

psadriyesterday at 9:28 PM5 repliesview on HN

I feel like this could be adopted for your homegrown "whatever" framework (eg: UI framework, Auth framework, …)

Congratulations on getting hired to this team! You probably count yourself lucky, but don't. We had been trying to fill this role for the past 5 months and every candidate would run away as soon as we showed them our homegrown auth framework. But don't run yet please, do give it a try.

So, you are still here? It must be a bad job market out there. Looks like you found the documentation for the project. Let me save you the trouble, it has not be updated since 3 years ago (about the time John quit). No worries, there are lots of usage examples in the Perforce repo. Perforce is like Git but that's for another day.

So you managed to checkout the code. Before you type "make", let me remind you to install this particular version of Python and set up your LD paths. Make sure you don't have anything else relying on Python because they will probably never work again.

If you hit the dreaded "std::vector<std::__cxx11::basic_string<char> > >'} is not derived from 'const char*'" error, ask Joe (if he is still around) to show you which header file you need to tweak. That's not checked in because it breaks the build on a legacy server we still have running for one of the customers.

… someone else please take over… :-)


Replies

dreamcompilertoday at 12:07 AM

> Make sure you don't have anything else relying on Python because they will probably never work again.

This is why when I see some clever open source tool discussed on HN and I go to the repo and see it's written in Python I close the browser window and pretend I never saw it.

Yes I know there are ways to protect yourself when using Python in much the same way that lead-lined glove boxes protect you when working with plutonium, but I can never remember the proper CLI incantation to make the lead-lined glove box appear.

show 6 replies
hinkleyyesterday at 10:10 PM

This would be perfect if you replaced “Joe” as the bottom with John to illustrate that this document has been edited five times and not brought back to consistency. And also that only one articulate person ever understood it and he got scared off.

> 3 years ago (about the time John quit)

> ask John (if he is still around)

show 1 reply
BLKNSLVRyesterday at 11:24 PM

Stop it!

... you'll need to refer to these pages on Confluence, but they haven't all yet migrated to the new Confluence documentation structure, which is here, so you'll need to search both. And then the really detailed documentation is in Sharepoint here, but when we update these documents we'll also need to convert them to PDF and publish them to our Customer-accessible ticketing system using this specific ticket number, which you'll need to remember because search on that system doesn't work very well.

show 2 replies
heresie-dabordtoday at 12:26 AM

> I feel like this could be adopted for your <organisation's management shenanigans>

Welcome to $org. Up to this point in the hiring process, you may have believed that we are a principled, well-structured meritocracy where all talent and hard work are appropriately awarded.

Well I find it necessary to inform you...

McGlockenshiretoday at 3:46 AM

There was a time when a previous employer looked like we were going to go down in flames -- 2008. I wrote such a love letter in the main include file (yay PHP) that told them how to figure out how the application worked and gave a credit blurb to all the previous devs and how they helped build the application.

We didn't go under quite yet and it was my extreme pleasure to allow two more devs to write their own blurbs and edit the letter to help future others. The company later went under and was acquired by a competitor, so I'm sure they've seen the letter in order to figure out how to extract data from the system. Effort not wasted.