Celarnor

Those are very high end ones I'd expect to see on commercial installations or homes of the ultra rich. Most landlords in my part of the US use the cheap regular off-the-shelf locks, where you can copy the key for a couple of dollars at Home Depot and throw the lock out once the tenant departs.

Me neither. I've never understood why it isn't illegal.

I wish I could work 12 hour days. :P

Did it ever mean something else? :P

This would be the ideal, but in practice (at least where I work) it would lead to empty offices all the time, since everyone would be constantly getting their regular 9-5 time "comped" dealing with whatever fires come up the night before.

Do you have any citations/references to support this?

All of my jobs have been as the GP describes, where managers see after-hours problems as the dev's responsible for the relevant feature's "fault", and expect them to both manage communication with business stakeholders about the problem and make it go away within short notice.

Interesting. At my shop we're all on call 24/7 for our features, but we aren't compensated extra at all.

Since the recession, the US' food insecurity numbers still haven't recovered to their pre-recession values. A disturbingly non-zero number of families have no idea when their next meal will be or where it is coming from.

> I understand how common this sentiment is, and maybe in some markets it really is true, but for the most part I just don't buy it that SaaS and eCommerce are zero-sum games.

I don't disagree with you, but it is shareholders & executives that determine how developer time is to be spent, not developers.

> If you're writing a web application, shouldnt you take care to make sure its secure and well written? Just because nobody had to pick hair out of a windshield doesnt mean a hacked webapp doesnt ruin just as many lives.

No. In fact, where I work (massive multistore ecommerce), this attitude is actively discouraged. They don't want developers spending valuable time worrying about what a malicious actor would do or how it can be protected against. That would be an inappropriate use of company time on non-revenue-generating activities. We HAVE to spend all our time feverishly implementing whatever features business put in for development this quarter to bump conversions and average order volume. If we focus on endpoint security, we aren't adding features, and so we might miss the revenue budget and then stuff REALLY hits the fan.

> An example: if im rebuilding the idler and pitman assembly on a fourteen ton truck, theres no hustle. there is no competition to do it "the fastest." You do it right, because if that assembly fails in a turn you could cause a pretty horrible accident.

In this scenario, you don't have to be in the situation of some company in some other country figuring out a way to sell people a machine that'll rebuild the idler 50% faster. In the SaaS & ecommerce landscape, being beaten to market or having a competitor that can iterate faster than you means you're dead.

For a good ten years or so, I thought Turkish Delight was a fictitious candy brand C.S. Lewis made up for the Narnia books.

In most states, no notice (or even a reason) is required. We call it 'at-will employment'.

This is why your SSH key has no business being in the filesystem and should instead be on a hardware token where all the crypto/signing operations happen on the HW token's chip.

Honestly what I'm thinking.

> ... but you don't hear a lot of stories of "I wanted to go to college but couldn't get a loan". Almost everyone gets approved, regardless of their future ability to pay it back.

This is absolutely not the case. Student loans have caps and they're incredibly easy to hit, especially if you go to a 5-year school where you're expected to pay tuition while doing 6-month internship blocks. Lots of people I knew in college (myself included) had to drop out in the first 2 quarters of year 5 because they couldn't get enough money to finish.

Edit: Just checked to see what the cap was at these days. Back when I was in school, the unsubsidized loan max was 27k. Now its 31k. https://studentaid.ed.gov/sa/types/loans/subsidized-unsubsid...

> What issues do they cause? Really?

Biggest one by far is the super-ambiguous "boot failed" with nothing else while trying to get back into windows after turning off Fastboot (see step 7 in my other post). Once you've got that, you can fix it for the next boot with bootrec /FixBoot & /RebuildBCD, but it'll keep coming back every time its restarted. Only failsafe fix I've ever found that keeps it from coming back is to move everything, including GRUB itself, onto separate disks. At that point it cooperates, at least until Windows thoughtfully turns FastBoot on for you again.

A close second is secureboot's "invalid signature detected". You get the same message when you try to chainload off a non-present drive or one that isn't bootable, but if you make the non-booting disk the only one, suddenly it'll start working again. Usually a grub2 reprobe/reinstall will fix this, but its really annoying. The dual-OS desktops at work all get this upon reboot whenever we lose power.

> Clearly annoying, but easily fixed.

Sure, until it resets itself at the next update, suddenly won't work when you turn it back off and you have to do everything all over again...

> I'd rather have this once a year than Windows deciding it has the right to write to my MBR, and overwrite GRUB, causing my Linux installation to be unbootable without a recovery-disk.

Only there's no risk of your linux installation being completely hosed in this scenario, like there is for the Windows environment with UEFI thrown in. Instead of starting over from scratch/backups, you just have to mount your drives, re-probe and install GRUB. That takes maybe a few minutes. Also, in a multi-volume system it can be completely avoided by disconnecting your dedicated GRUB disk for windows updates; the same can't save you from Windows declaring itself king of the computer and suddenly turning on UEFI settings that you don't want.

> That may be true for multi-volume scenarios. For systems with one volume only however (like most laptops), it's absolute the opposite.

Its worse on single-volume scenarios, since you can get completely screwed. In a multi-volume environment, UEFI's fragility is somewhat compensated for by the fact you can boot off the boot sectors of the individual drives when it breaks.

> My experience is quite the opposite. With UEFI I feel I can fearlessly dual/multi boot several operating systems without fear that one OS is going to mess up another one.

Huh. Yeah, that's ... pretty much the exact opposite of the experience I and everyone I know has had. You're honestly the first person I've seen that's been a fan.

There's garnishment limits. Since they have to leave you with at least 30 hours worth of minimum-wage earnings per week, a lot of people who can't afford their loans are effectively un-garnishable.

Doesn't matter to the lenders, they've already written off the loan and reassigned it to government student loan debt collection at SLM.

This licensing thing is something the government can do when the loan gets reassigned to it during collections. They do other stuff, too. If you have property, they can put a tax lien on it. They can seize your tax refunds or any cash benefits disbursed by federal government programs, like Social Security. Pretty much, if there's something "government" can do to screw you over because you can't afford your loans, they do.

Can't really speak as to issues with single-OS installs. Those usually go alright. The problems I always run into arise when you try to go and install another OS alongside what you've already got (usually Windows, but I have seen the same kinds of UEFI issues with OS X+Linux and OS X+Windows+Linux). With legacy boot, this is relatively easy and goes something like this:

1) Resize existing filesystem, setup new partitions

2) New OS installation

3) Install GRUB over MBR

4) Boot whatever you want. Enjoy your multi-OS computer. Install more operating systems, whatever. GRUB has everything it needs to figure it out and edit /boot accordingly.

With UEFI, it goes like this:

1) Resize existing filesystem, setup new partitions

2) New OS installation

3) Install GRUB2 over MBR

4) Realize you can't boot into new OS because of UEFI's "next boot" flag used by Windows 8+'s Fastboot/Fast startup option.

5) Realize you can't get into old OS either because secureboot is still broken for multi-OS environments.

6) Mess around with Windows Recovery Essentials. or an OS X Recovery System. Restore original boot sector with bootrec/Disk Utilities. Disable fast startup in BIOS.

7) Hopefully boot back into windows again. Sometimes the original Windows installation doesn't like the altered UEFI settings and you can't. When that happens I resort to re-installing each OS to separate hard disks, each with other OS' drive disconnected during installation. Then add another disk for GRUB2. Re-do GRUB2 probing/installation. Then...

8) Disable fastboot in windows, cause UEFI is dumb and will let windows turn it back on. Probably mess around in bcdedit.

9) Load linux installation media again. Redo GRUB2 OS probing and installation, unless they're all fresh installs from step 7.

10) Hope everything works right at this point.

11) Wait for updates for your original OS to break everything, permanently lock you into booting just the original OS because of the terrible idea that was nextboot. If everything's on separate drives, you might be able to boot them independently from BIOS, and just have to disable settings again. Or not, because of the same "hey, this is a different computer, I'm not going to boot" type of stuff that can arise in 7.

12) Start again at step 4...

It works fine except when it doesn't, which is most of the time (either secureboot, or the EFI boot manager, or the Windows 8+ "fast startup" thing that can turn itself on during an update and sets the EFI next-boot option, permanently overriding any GRUB selection until you turn it back off from inside Windows..)

Compared to how hassle-free multiple operating systems is to do via legacy boot, UEFI feels incredibly backward. It feels unfinished, is fragile and breaks far too easily for something so critical.

I'm not looking forward to it being taken away. Guess I'll have to ditch my other OSes and do my important work in a VM.

As a millenial, this is pretty much how I'm trying to live my life, just with a "I'm good" point at 35 instead of 45. By that age I hope to have a trailer and enough land for subsistence farming all paid off. Then any employment that I'm lucky enough to find in my old age will be extra income instead of something I have to find to survive.

I'm 'only' 28 and I worry constantly about this as 30 gets closer and closer. When you're the oldest developer you have to work much harder to justify still being employed, but not so hard that they start to worry about you jumping ship for 5-10k more.

The only people around my company that are around your age are the owners and the directors that report to them.

Most of the people I know in tech feel like they're aging out of the market. Small web/marketing agencies--the only development jobs available around here--want fresh grads for junior positions. Most of the time those are the only ones available, as there is rarely more than 1 or 2 lead/senior developers within the company.

I've never heard "you're overqualified" specifically, but I lost count of how many times I heard "we can't pay what someone with your skillset is worth and don't think you'll stick around because of it" when I was unemployed between jobs #3 and my current one for 5 months, desperately applying to any and all positions that got posted, like 'website maintenance assistant', 'adwords manager', 'forms developer' and 'frontend developer'.

Eventually two weeks before my unemployment would have run out, a senior java ecommerce developer position opened up, to which I currently cling with dear life. :)

This might just be regional/bad job market thing, I don't know. Never lived anywhere else but Maine.

Same. 'Going out' is just stressful and/or depressing.

This doesn't work for everyone. Some people are just not good at being deceptive like that.

I have strong social anxiety that is at its worst in interview situations. When I try to 'edit' my answers to questions like that instead of giving a straightforward and honest answer about the stuff I've built and the experiences I've had building, my brain spins endlessly trying to model all possible 'edits', the possible responses, and possible counter-responses.

> Should hiring decisions be entirely divorced from context?

If by 'context' you mean things not related to the applicants ability to do the job, yes. They don't have anything to do with the ability to do the job.

> Should employers not worry about anything but 'can the person do the job right now'?

No, they should not. Whether they can do the job is your first and only concern.

There are so, so many reasons why someone might be forced to take a less than 'optimal' job. Maybe there are no appropriate jobs in the area available anymore and the applicant is trying to switch fields to one where they can find work. Or maybe they have a family now and can't do the 70-80 hour work weeks for lead dev positions they could do when they were single. Or maybe they've developed anxiety from having the weight of a business' systems lying on their shoulders alone and want a generally easier gig. I've known people in my peer group their late 20s and early 30s that found themselves in all these situations.

These are not the applicants fault, and to reject him on that basis alone makes no sense.

This is fascinating to see.

I'm only two years away from the cliff (30), so every day I worry if the development job I have now will be my last. I'm a hard, dedicated, loyal worker who has never left a company, only swapping jobs when my old employers laid me off or themselves collapsed. Unfortunately, I suffer from strong social anxiety so management certainly isn't an option.

When I was 22, finding a job was easy. But once you have the portfolio they say they were looking for in the first place, no one wants you anymore because they're too afraid you'll jump to the next job paying $1k a year more or whatever. Its dumb.

This is fascinating to see.

I'm pushing 28, so every day I worry if the development job I have now will be my last. I'm a hard, dedicated, loyal worker who has never left a company, only swapping jobs when my old employers laid me off or themselves collapsed. Unfortunately, I suffer from strong social anxiety so management certainly isn't an option.

When I was 22, finding a job was easy. But once you have the portfolio they say they were looking for in the first place, no one wants you anymore because they're too afraid you'll jump to the next job paying $1k a year more or whatever. Its dumb.