My biggest mistake after being laid off was to not be discerning enough about my next job. You need to be willing to say no to a crummy job offer, even as the bills pile up.
Nit: you're never in that position in blackjack. You only double when you have 9, 10, or 11, but you'll always hit that anyway. Some bizarre casino could theoretically let you double Ace-10, but that's just getting greedy.
A temporary consulting gig is better than a bad job offer. It also doesn't stain your CV (Consultant doing something for a client vs Working at this horrible place) even if it's the same client.
I would disagree. Consulting work exposes you to more liability than being an employee. If you drop a consulting job midstream to take a great job offer, you're likely to get sued.
As someone who was contracting we always had notice periods in contracts. Let’s not forget it works both ways and contractors are more often than not the first to go.
When I was freelancing, I would have a Master Service Agreement that spelled out the "rules of engagement" and the actual work was in a Statement Of Work that lasted roughly 3 months. Gave each party the ability to pull the rip cord
I’ve done consulting; you have control about how you write your contract. If they want to lock you up for a long period they should be willing to pay for it.
Could you elaborate on that? I would think maybe in the very short term if you have minimal expenses and some savings, you have a bit of time to be picky, but not if you've got major expenses, dependants, or just very few offers coming in.
Like don't go agreeing to an obviously terrible offer, but this isn't a seller's market anymore.
John, at around that time you mentioned, you gifted me with my first shell account on one of your coffeshop servers, Reva. I just wanted to say THANK YOU. Up until then, I had read books about unix from the library, and had failed to install Mandrake on my laptop, but being able to access such a well configured NetBSD environment was really helpful and set me on a good path.
I had never been truant from school before up to that point, but sometimes life rewards you for taking risks.
You know, I'm still running servers with many of the same accounts that were there twenty years ago. Your home may still be on one (with the password disabled, obviously). Write me directly and let's see!
My email address is my first name @ my last name dot com, and my handle here is my full name.
Linux was good for me too, I escaped SCO and then dodged the bullet of NT.
It was so nice to switch from being tied to wires, to many hours with table service at local coffee shops in santa cruz like the Perg, and 420 union, in Santa Cruz. Sadly, both are gone now....
I was hoping that using hardware keys would eliminate some of the security hoops that we have to jump through. And it does seem to help. But the whole reason that I have a key is so I do not have to supply my phone number, and I have a more trusted way of proving my identity, even if I am connecting from an unusual location.
No, that is not correct, git-annex uses a variety of special remotes[2], some of which support deduplication. Mentioned in another comment[1]
When you have checked something out and fetched it, then it consumes space on disk, but that is true with git-lfs, and most other tools like it. It does NOT consume any space in any git object files.
I regularly use a git-annex repo that contains about 60G of files, which I can use with github or any git host, and uses about 6G in its annex, and 1M in the actual git repo itself. I chain git-annex to an internal .bup repo, so I can keep track of the location, and benefit from dedup.
I honestly have not found anything that comes close to the versatility of git-annex.
Of course, it uses pointer files for the binary blobs that are not going to change much anyway.
And the datalad project has neuro imaging repos that are tens of TB in size.
Consider whether you actually need to track differences in all of your files. Honestly git-annex is one of the most powerful tools I have ever used. You can use git for tracking changes in text, but use a different system for tracking binaries.
I love how satisfying it is to be able to store the index for hundreds of gigs of files on a floppy disk if I wanted.
For bigger annex repos with lots of pointer files, I just disable the git-annex smudge filters. Consider whether smudge filters are requirement, or a convenience. The smudge filter interface does not scale that well at all.
I combine git-annex with the bup special remote[1], which lets me still externalize big files, while benefiting from block level deduplication. Or depending on your needs, you can just use a tool like bup[2] or borg directly. Bup actually uses the git pack file format and git metadata.
I actually wrote a script which I'm happy to share, that makes this much easier, and even lets you mount your bup repo over .git/annex/objects for direct access.
I never use split-screen view for Markdown. Split-screen makes sense for something more abstract like latex or html. But I do not see the benefit for Markdown. I would much rather have 50% of my screen.
Not just are they using basic http auth, but it is silently ignored by the server. Try it yourself.
They clearly intended to impelement authentication on their API endpoints, but didn't finish it, becuase the client is sending an Authorization header. But I don't know if their servers are even configured to check them. And they should certainly use JWT instead of digest.
