304 karma · joined September 23, 2016
They fuck you up, your mum and dad. They may not mean to, but they do.
They fill you with the faults they had And add some extra, just for you.
But they were fucked up in their turn By fools in old-style hats and coats,
Who half the time were soppy-stern And half at one another’s throats.
Man hands on misery to man. It deepens like a coastal shelf.
Get out as early as you can, And don’t have any kids yourself.
Effectively, they test things to destruction, then publish minimum requirements. So if you want to pressurise your reactor vessel to reactor vessel to 30 atmospheres, you can pretty much look up a table that'll tell you precisely how thick the reactor walls need to be for each of the commonly used materials. If you want to use something uncommon, then you need to pay somebody to test it.
If it fails in a catastrophic fashion, you can expect to be asked to show that you did your due diligence, and there are extenuating circumstances a reasonable engineer could not have been expected to foresee and plan for. Or that you did foresee it, and somebody else chose to accept the (clearly defined) risk.
Personally, I'm reading the README and/or looking at the contents of files. Plus looking at issues. Very rarely am I looking for the releases tab.
I'm amused that people are using the "I only do this every 6 months so I can't remember where it is" argument. If you only need the functionality every 6 months, perhaps not having it in your face every time you use it might be a good thing ...
Conditions might be rarer, but the steps aren't solely reliant on the absence of microbes which now exist.
Also, I contend a good programmer who's been out for 10 years still has the ability to be a good programmer. Sure, they're not going to know whatever language/framework is popular this week, and they'll probably be slower to pick up a new one than somebody who's up to date, but I contend they'll be productive in less than a month.
Eventually. At first it makes matters worth. And that's assuming your predicate is correct, that the department is understaffed.
It feels like more efficient screws (which are incidentally quieter) would be a fairly popular sell to the shipping industry.
If relying on IT makes you a tech company, then basically everybody is. If what you provide is technology, then maybe you're a tech company, if what you do is provide a banking service, you're a bank. Try running a bank without using modern technology to the limit ...
They leverage some damn impressive technology, but their business is about delivering media for end user consumption, much like any of the TV companies during most of the 20th century, for example.
You might think it's a sprint. You're wrong.
If you can outsource your driver to somebody like Deliveroo or Uber Eats, even better ...
If it's remote, I'll ask them to share their screen with me with a project set up and ready to go, having emailed them a copy of the interface we're going to implement about 30 minutes before the interview.
Also, how much of their day-to-day work is going to be setting up new projects? I sometimes feel a better test is to be thrown into an existing code base and asked to make a change. It's far more indicative of the sort of work somebody is likely to actually be doing.
In general, if I'm asking them to code on my (or the company's) hardware, I'd start from an existing project, if only because I wouldn't expect them to be familiar with the installed tools (oh, you use maven? I'm a gradle user ... etc.) On their own laptop, I'd expect them to be more comfortable.
I'm doing a remote interview on Wednesday. That'll be on the candidates machine (because screen-sharing is easy, getting them inside the corporate network, not happening), and they've been told they'll need an IDE ready to go. I'll expect a project set up and ready to go before the call even starts.
I tend to give candidates a simple project already to go, with junit and hamcrest, possibly mockito already available, and ask them to go from there using a provided IDE (which I attempt to get set up as near as they prefer to work as I can). This generally works out fine. I certainly don't feel the boiler-platiness of the language gets in the way, mostly because the IDE is generally capable of doing most of the lifting with that respect anyway, but also because over the timescale of an interview question, we're generally only talking about a couple of classes at most.
Yes, they still have an impact, but it's less than the impact they'd have had if they bought an equivalent petrol/diesel vehicle.
People who regularly change their cars regularly change their cars ...
Not to mention the overhead of running Jenkins at the kind of scale they're talking about here. We're not talking about small numbers here.