524 karma · joined February 16, 2009
I do think it was an interesting option to replace the SRBs on SLS but alas we'll never know.
Over the years, I've also looked at the Dell XPS 13 developer edition and the Purism. There was a system 76 model I was looking at too, but went with the Framework
I had a 2012 retina MB pro and it was (so far) probably the best machine I've ever owned, but I use an m2 MB pro for work and I would not buy one for myself.
Free(Libre) software has never been about price. Typically any price/code is either
- For some kind of support contract (eg for pro users, SMB, or enterprise)
- Open Core/Pro (closed source) version
Yes, others can compete with you. If you're worried about this, then don't open source.Also, so called source available languages do not meet the definition of both Open Source or Free/Libre software.
Most companies will NOT deal with GPL since it's such a grey area around the implications, which is why dual licensing might be an option.
Lastly AGPL or GPL3 is really GPL with a clause specifically around web/cloud hosting.
That IS my local/personal convention. It comes from my Amiga days where we had a second partition called work: (no home directories remember). I never liked ~/Documents very much but ~/work performs the same purpose.
For me I just run the ddl (sitting in a .sql file) and run my tests. They run with an empty db but I could have sample data too the same way.
They were my first hire and made a number of mistakes:
- I was too nice/eager (one of interviewers said 'no, they can't code' and I should have listened to them).
- They passed (with the one caveat) our not very rigorous screening process, this is on me as well.
- I did not do a formal review at the end of their probation period (it was becoming obvious they were not skilled, but I dismissed it as coming up to speed with our systems).
The pip was intended to show me they were capable of being in the role, but they cheated and I can't abide that.Before the pip, I would have probably kept them but with a pay cut, but prevailing wisdom was that it would not work in practice.
1) got a talking too about performance - it wasn't called a pip (my mom was dying and I was taking too much time out for medical appointments for her. Note the discussion was shortly after she had passed)
2) As a fairly new manager (at the time) I had to put my first hire as a manager onto a pip. It was painfully obvious to everyone they were not capable and struggled with the most basic things.
While I didn't hold out much hope they would turn it around, I gave them every opportunity to prove to me they could do the job (or learn at least to) they were hired to do, instead they cheated their way through the pip, passing others peoples work off as their own.
There are few secrets, just common sense really:
- Live within your means (spend less than you earn), avoid debt.
- Corollary: Have a good paying job (tech is handy for this)
- Save early put 10% (at least) of your gross salary into investments such as low MER ETFs, re-balance every 6 months - or use a Robo Advisor that does it for you.
- A partner/spouse helps immensely (and you both need to be aligned wrt goals and spending habits!)
- Balance savings and the future with enjoying life
(edited for formatting)I set up a NetBSD VM (on my Macbook) that I had intended to use but there was just enough friction/lack of pkgsrc knowledge that I never made the leap.
1. Employees (eg people who get a 1099(?)) would seem to require a green card or visa. 2. A contract employee is more of a business relationship but avoids the above requirements (if any, I am no expert which is why I asked :) 3. A Canadian entity would issue a T4 slip and also avoids any visa requirement and has none of the downsides of doing things as a contractor. But it requires the parent to have created and registered a company here.
I currently work for a US parent with the 3rd option (we were acquired). Engine Yard (not me, but I knew people there) used option #2.
"Our own web console, CLI, and SDK consumers (e.g., oxide.rs, oxide.go)"
The other project I'd be interested in working on (likely as an open source, separate project) would be bringing the dx/ux and tooling to home lab level gear.
Is there a Canadian subsidiary or is it a contract employee kind of relationship (if you can comment!)?