Absolutely. I worked a codebase that was littered with ticket numbers for a few years; many members of the team religiously added them but never read them. How do we know? Self hosted issue system and access logs. New starts would read a couple and that was it.
A ticket is a really opaque way of showing something. If you click the issue you're now going through several tangentially related comments and a few MR back and forths just to work out if its even useful to you. People will stop bothering to even open the link unless they are really stuck.
Whack a summary comment and then by all means include the link, but the comment is what most people will use.
Yes. Unless your explanation is thousands of words (which it probably shouldn't be), just inline it. I only speak for me, but if I had to look up (potentially multiple) Jira tickets just to understand what was happening in a source file, I wouldn't be at that job very long.
That depends on whether or not you think the Jira ticket will outlast your code or not. If the company will definitely never replace Jira then no. If there is a chance that they will, and for your sake I really hope there is, then you'll need a better comment.
”Containing an Internet browser, email & newsgroup client with an included web feed reader, HTML editor, IRC chat and web development tools, SeaMonkey is sure to appeal to advanced users, web developers and corporate users.
Under the hood, SeaMonkey uses much of the same Mozilla Firefox source code which powers such products as Thunderbird. Legal backing is provided by the SeaMonkey Association (SeaMonkey e.V.).”
This is the open source version of Netscape Communicator circa 1997. It is mozilla.org's first and oldest open source browser client. That client was eventually split in to Firefox (browser) and Thunderbird (the rest).
It has all the features of Firefox, plus built-in support for your favorite social media newsgroups, email, and contacts.
Neither this comment nor my sibling mentioning Netscape 5 are correct. SeaMonkey's lineage is Netscape 6. Netscape 6 is from the early 2000s, not the late 90s. This is significant because they are different codebases, and there was a substantial gap between the latest mass market release in the 90s and the first release prepared from the new (nglayout, now known as Gecko) codebase. The code that was first released in the 90s was the then-in-progress state of the never-finished Netscape 5. The decision to scrap Netscape 5 is the source of the "never do a rewrite" meme that came out of Spolsky's article.
At a previous job I had different Linux boxes I had to run a browser “on the box” through ssh connections. Both FF and Seamonkey have socks proxies in their UI so it was handy to have both to point to different machines.
* Database schemas - warehouse, OLAP, and (planned) the ETL script between them.
* Application models (for ORM etc) - the rails one is implemented.
* Code generation for serialization / deserialization from the shared domain model.
* (planned) automatic query extraction from type-safe templates (you write your template in terms of the domain model, and it gets automatically compiled into a set of database queries which supply the data it needs).
It's hard to learn, which is a hefty up-front price to pay, but it neatly avoids a ton of work 12+ months down the track.
It's entirely P2P, so no 3rd party hosting of your files, no trusting someone's crypto/update schemes, or having to set up your own servers (although you still can easily add it to a VPS if you want offsite). There's also a nice mobile app:
You can also securely share directories with another person who uses Syncthing, I've found autosync directories are easier than using something like Airdrop for sharing photos with family.
I'm using them for years as a form of backup. Very reasonable priced, works flawlessly for me though I mainly use as a form of backup for a synced folder. GDPR compliant.
I've seen a HN poster promote filestash.app which looks like it's either self-host or hosted. I guess you might have to add in something like Spideroak, Backblaze, or tarsnap if you want to self host + backup.
Or Syncthing as others have pointed out.
I'm still thinking which is best. They're slightly different use cases. But generally, I'd only really trust it if there's open source, otherwise there's lock-in.
#1 starts with not doing the same thing multiple times needlessly (so automate), then it is about mentoring others to do your job (and in general), plus being 100% transparent about what you are doing. Part of mentoring IMO is also raising your hand to help someone else that needs it, but still making sure you deliver on your commitments.
People that hold onto information to try and keep their position are the exact opposite of this idea, probably everyone has worked with someone like this. The dude that "hides" credentials, or says he'll do it cause no one else can etc.
You want to share everything you know and be transparent. It scares some people because they fear they'll be replaced if they do this, but the reality is you can't move on to the next level unless you've made yourself replaceable.
I don't honestly think it is more complicated than that to be fair.
One other nugget to all of this is you have to trust others to do their job, and when things break you have to take responsibility and help pick up the pieces even if you weren't the reason it broke. I think most good people take responsibility, but I know a lot of very capable and intelligent engineers that will never lead a team or be a CTO because they have the complex that only they can do a job correctly. We can approach a problem 2 different ways with tradeoffs each way, but if I am the CTO/director etc and I give you a project to do, along with some direction of course, I need to trust you (assuming you can defend your solution fairly) to do the job. A leader can't micromanage and succeed long term, it just doesn't work. And that is all part of making yourself redundant in my view.
It's probably worth it in your case, but you'll need to be very careful about planning how it directly gives you an increase in return on investment. College is ridiculously expensive in America nowadays, and I would be very hesitant to go back if I wasn't certain it would lead to a drastic increase in income.
