You may not even get as far as an interview. More and more, I see job applications asking whether you are subject to non-competes, alongside asking about visa etc. I imagine answering yes will unceremoniously move your application to the reject pile.
It just means your start date is delayed. No different from interviewing a student whose graduation date is a year away or interviewing a foreigner who might require a few months of paperwork to get a work visa.
Most non-competes are at least 6 months but usually more than a year, and I have never worked in a company that was open to hiring someone with a start date that far in the future. Plus, the clock wouldn't even start running until they leave their job, so if you hire them for a start day in 12 months, they have to quit now and spend their savings. I have never met someone who was open to doing that. I am sure it could happen in very rare circumstances, but most jobs would be closed to most people with non-competes. I am glad that I live in a jurisdiction that doesn't allow them anymore.
That’s not at all my experience. I remember back in the college days every single company on campus was willing to interview students in fall knowing that they would graduate next summer. That’s at least 9 or 10 months of waiting. Because if a company waits until spring, all the best students already have offers and aren’t on the market any more.
> they have to quit now and spend their savings
Every single job offer I’ve seen with a non-compete is a paid non-compete. You get 100% of your base salary and zero bonus. In industries where non-competes are common, people know this. They have savings to deal with reduced income due to zero bonus. There’s a reason why the non-compete period is colloquially known as garden leave. You have enough savings so that you can literally work on your garden. Companies know they need to be patient and plan for hiring needs far in advance. It’s super predictable.
Same here in Canada. I have had three non-competes in my career, none of which were paid. All of them were probably unenforceable if it went to trial, but I would have never gotten that far in the hiring pipeline. I instead opted to switch industries and move to a jurisdiction that doesn't allow non-competes.
According to the article, the law says B. If that makes for bad law, it's up to the legislature to change it, not up to the retailer to unilaterally decide to stop following the law.
Actually, the article says the law says A or B. From the article:
> In a simplified form, retailers are responsible for warranty claims and must replace or refund the defective item
The choice is at the retailer’s discretion and the refund is obviously of the purchase price.
This is a non story. The retailer is acting lawfully. The only curiosity is that normally it is in a retailer’s best interests to replace goods, but in these circumstances they are better off refunding them.
Something about people successful with computers makes them quick to claim something is easy based on the number of steps needed, without regard to the ease of remembering all the arbitrary or sometimes contra-pattern steps required.
In my defense, I remember it because I expect Option key to modify the original character and Shift key to make it bigger, so remembering that Option plus Shift makes hyphen into a bigger alternate version of it, i.e. the em dash, is not difficult. I acknowledge that not everyone would see it this way.
First of all, thank you for making this. I used it in my recent job search and it was fantastic.
Second, if I may make a request, could you please follow SemVer? I tried rendering my resume again last week, only 3 or 4 months after having made it originally with RenderCV version 2 point something I cannot recall, and it would not work. The design schema and perhaps also the CLI options have changes so much that I expect I would need to spend 2 to 4 hours getting it to work again, and there is no guarantee that it would not break again in another month. I would have appreciated if the versioning scheme followed SemVer, so I would know that any v2 engine would work and v3 engine would not.
I also would appreciate it if you could write detailed migration docs between versions and/or recommendations in error messages. The reason I think migrating my CV would take so long is that I have to go by trial and error, searching for similar-sounding parameter names and replacing them one-by-one. I gave up after an hour of this as I was nowhere near done.
Third, is markdown render supposed to miss information or is it a bug? Some sections of the resume would not end up in the markdown version, only showing section title and nothing else. If this is not expected behaviour, please let me know.
Again, thank you for making this. I look forward to using it again in the future.
Thank you so much for the kind words, and I'm sorry for the trouble the changes caused you.
To give some context: I hadn't worked on RenderCV for about six months, and when I came back, I had grown technically and my design taste had changed. I decided to do a significant overhaul rather than preserve backwards compatibility. It felt necessary to maintain my enthusiasm for this project long-term.
You're right about semantic versioning. I used a two-number scheme (MAJOR.MINOR) back in 2023 when I didn't know much about releasing software. By the time I understood the benefits of MAJOR.MINOR.PATCH, I didn't want to change it mid-stream. I'm planning to switch after v3. It will give me more flexibility to tag updates appropriately.
I'm also adding migration documentation to my list. You're right that I should have done this. Going forward, there will be clear migration guides.
Regarding the Markdown issue where sections show only titles, that sounds like a bug. If you could open an issue with details, I'd appreciate it.
The author discovered AI coding 2 weeks ago and completely went to town on the entire project. If you use any version before this (2.2) it will probably work fine.
Thank you for writing this post. Your writing is insightful and thought-provoking. I would love to follow your blog to read your future posts as well, but I could not find an RSS feed or an email newsletter option. Is there any chance that you would add RSS to your blog in the future?
I can see the logic. Layoffs are always terrible. But if I am getting laid off anyway, I would prefer to know about it before I spend a whole bunch of money during holidays.
I have never had a heat pump, so I wasn't aware of this shortcoming. Could you please explain a bit more how different it is with heat pump compared to furnace?
The heat pump will always produce air that is warmer than the temp in the house, but as the temp outside drops the temp of the air coming out of the vents also drops. So on a very cold day when the house temp is say 70F, the system might only be putting out air that's 75-80F. The air coming out of the vents doesn't really _feel_ warm and it may take an hour or two to raise the temperature in the house when you wake up or get home in the evening.
In my experience at least with relatively modern heat pumps (roughly 2000 and newer) it doesn't matter that much when outside temps are above freezing. But it quickly starts to become noticeable as temps drop into the 20s.
I see. Thanks for the explanation. So the system is slow to come up to the set temperature. Is it good at keeping the temperature though? After the house temp gets to 70, does it consistently stay at 70, or are there shortcomings in this aspect too?
reply