$ zdump -Vc 2025,2026 America/New_York
America/New_York Sun Mar 9 06:59:59 2025 UT = Sun Mar 9 01:59:59 2025 EST isdst=0 gmtoff=-18000
America/New_York Sun Mar 9 07:00:00 2025 UT = Sun Mar 9 03:00:00 2025 EDT isdst=1 gmtoff=-14400
America/New_York Sun Nov 2 05:59:59 2025 UT = Sun Nov 2 01:59:59 2025 EDT isdst=1 gmtoff=-14400
America/New_York Sun Nov 2 06:00:00 2025 UT = Sun Nov 2 01:00:00 2025 EST isdst=0 gmtoff=-18000
$ zdump -Vc 2025,2026 Europe/London
Europe/London Sun Mar 30 00:59:59 2025 UT = Sun Mar 30 00:59:59 2025 GMT isdst=0 gmtoff=0
Europe/London Sun Mar 30 01:00:00 2025 UT = Sun Mar 30 02:00:00 2025 BST isdst=1 gmtoff=3600
Europe/London Sun Oct 26 00:59:59 2025 UT = Sun Oct 26 01:59:59 2025 BST isdst=1 gmtoff=3600
Europe/London Sun Oct 26 01:00:00 2025 UT = Sun Oct 26 01:00:00 2025 GMT isdst=0 gmtoff=0
I have a Logitech G700s mouse with 9 or more programmable buttons and different profiles based on the window in focus. My most useful mouse binds are copy/paste/enter buttons, backspace on the wheel tilt left. Win+tab on wheel tilt right helps to move around open windows very quickly. Also have 'q' and 'exit' for when I'm perusing terminal windows without my hands on the keyboard.
Paired with a G15 keyboard with a plethora of buttons, which include shortcuts to my most common applications as well as switch desktops left/right.
Exact same experience about a year ago, I also passed up the deal and ultimately concluded later that it was legit. I then emailed PG&E telling them that whoever is doing this is training people to trust a random, pushy person at the door who shows nothing other than a badge and iPad full of content.
As a current seeker of a remote position, and based on the relatively small amount of responses I've been getting, I feel like I might be falling into that bucket of applications that appear low-effort. What indicates to you that an application is low-effort?
Relatedly I wonder how much a high effort canidate vs a low effort canidate actually works out in a screening process despite whatever prejudices they may hold one way or another.
It reminds me of the recession bad old days where some companies were making a policy of hiring only the already employed and got essentially an exasperated facepalm from congress asking if they /really/ will have to ban hiring discrimination against the unemployed.
How does one tailor a resume to a specific job without bending the truth? I don't have experience with the exact stack listed but I bet I could get up to speed within a week or two given the chance.
edit: And what does tailoring to a specific job mean? Should I change my job titles to match? Do I just copy a bunch of keywords from it into my descriptions? I've never worked that specific job that is why I am applying
Remove irrelevant positions and focus on projects that match the target.
Assumedly during your career you have done multiple small projects on one topic or another, highlight the ones that interest the employer and the ones you feel particularly proud of, don't mention the others.
An interesting point. But employers should start giving out instructions on what they want to see.
I had a few employers tell me that my resume of 5 pages was not long enough and others that complained about too much information.
So... This provide only relevant information is as valuable as keeping quiet.
When you advertise a position, do you inform what form the CV should be in?
The hiring process is de facto a completely subjective system of both sides hoping the other would screw up to make their decision easier, while playing mind games.
I interviewed at Bridgewater on site, their interview was awesome and clear. More companies should be that clear and forthcoming as Bridgewater Associates.
Hello! I'm Chantal, a Junior Technical Recruiter from GitLab. Some other folks have provided great thoughts on this subject.
In general, I think you have to understand your audience. If you're applying for a job at a large company, or one that you know receives a ton of applications, you should find a way to stick out. Also, the recruiters likely won't have enough time to read through a 5 page resume. If you're applying to a smaller company, that long resume and cover letter might not be a bad idea. I asked my teammates to add tips about resume writing since I'm going to be helping out some bootcamp graduates soon. Maybe it will help: https://gitlab.com/gitlab-com/people-group/recruiting/-/issu...
If the position requirements describe certain things they want and you have done those things at certain jobs, basically say that you have done what they are asking for at those jobs. Things like "work on multitier web application" or other items that are not stack specific but that you have done. Include text closely matching those descriptions at jobs where you've done it.
If you don't have the experience I don't know how you'd craft it to be honest except for perhaps being descriptive in the cover letter about how you don't match everything but what you are able to offer and why you may be excited to work in the specific role at the company.
While you can definitely tailor your resume, it's as much about not applying for jobs you really aren't qualified for. When we tried to hire for a Postgresql role, we got tons of Excel and Access people that couldn't spell Postgresql. If the job is for an AWS expert, and you're a Rails developer whose AWS experience is using an S3 gem, don't apply.
+1 to this. I have a board with different lists regarding the overall category of the idea. (App, website, thing, etc.) Along with that I use labels to further categorize within the lists.
This sounds like the Volt. It is software limited to only use the "sweet spot" charge range of the battery, so that it never gets fully charged or discharged. This means that over time as the battery degrades, the user would still see the exact same range due to the system expanding the min/max allowed charge.
Yes, it let's them know that this issue is a priority, and that they can gain popular support by either reemphasizing their position, or by sponsoring a new bill.
In this situation, the representatives didn't vote. They shelved the bill, A.B. 375 [0]. Many bills don't get put up to a vote because they aren't seen as priorities or viable. This includes SOPA/PIPA which was one of the most bipartisan co-sponsored bills [1] and yet never made it to a vote because of the popular outcry such as the Internet blackout day.
Also, I love the idea of providing 3d models for something like this that needs to be perfectly sized