In Germany now there are laws in place for this, you get ridiculous stuff like as consultant you are not allowed to eat together with team mates from the employer because that is seen as bounding activities (you may "accidently" bump into each other in the cantine, but not go together), or share the same office equipment for coffee, having to go down the stree to get coffee while employees get theirs from the kitchen, and so on.
Nothing ridiculous about it. That came out of the permatemp lawsuits in the US by contractors a couple of decades ago which resulted in employers avoiding doing anything that made it look like contractors were being treated like permanent employees. Squeezing for money by a few contractors ruined a good thing for the rest of them.
Why is that ridiculous, I work in consulting. Why would I expect to be invited to the Christmas party? If you had consultants from McKinsey working for you, would you expect them to be invited to your Christmas party?
Because in a lot of places the consultants and employees work side by side, sometimes for a long time, on the same project/work. They operate as one team, more or less. The consultants are more like staff augmentation, than McKinsey consultants.
If I was a manager of that team, I'd worry about the effect of treating part of my team differently.
If I was an employee on a team like that, I'd feel really bad about my team mates not being allowed to participate.
There is admittedly a difference between staff augmentation and McKinsey style strategic “consulting”. The distinction is usually who owns the project?
If the client company owns the project and you are just coming in as a warm body, that’s staff augmentation.
But if the client company is putting out Requests for Comments to different companies and they sign a Statement of Work and your consulting company comes in and does the work, that’s “consulting”. In the latter case, you don’t usually get let go as soon as there is no work for you - ie when you are “on the bench”.
Even if you are a more junior employee at the latter company where you are more hands on keyboard than flying out to meet customers and sometimes you might even be doing staff augmentation for the client, it still feels differently.
My consulting company has internal employee events, is responsible for my pay, performance, etc - not the client.
No experience with McKinsey directly (thank goodness) or any consulting groups like that, but why not invite them to the holiday party? But certainly we should invite "Sheryl from accounting" who is technically a contractor, or the janitor who works for the landlord. These people are coworkers, whether or not our paychecks have the same signature on them.
If you were working with a general contractor where you signed a contract with them and they just went out and led the work and kept you updated with statuses, would you invite them? Would you invite the subcontractors? The actual construction workers?
This how true “consulting companies” work. You sign a statement of work with the requirements and costs and then they (we) go off and take care of staffing and lead the project. Your company will probably never interact with anyone besides sales, the tech lead and maybe the people over sub projects of the larger project (work streams) and their leads.
OK sure, but I never once mentioned any of this and have no idea what the social customs are around hiring general contractors to build buildings or asking CIA-adjacent consulting companies how to jack up the price of bread. I just know that half my coworkers have a slightly different email address for "legal reasons", and they aren't allowed to come to the Christmas party. This is, in my opinion, simply mean. Basically we seem to have invented a kind of at-will apartheid that 0.0001% of the population understand and even fewer benefit from.
That’s staff augmentation which is completely different. If your company doesn’t know anything about Salesforce for instance and you just need a one off large project, you are going to hire a consulting company to go off and do the work and leave.
It doesn’t make sense to build the competencies in house if that’s not your core line of business’s
I left our part of my explanation of a general contractor. I meant when you are having a physical structure built like a house or in the case the analogy would be adding on to your office building
Many companies use consultants as easier-to-fire employees. I've occasionally worked with the same consultants for years, with them acting as team mates doing the same work as every other internal. And we were team mates in everything work related, except the parties.
I understand the contractual and financial logic but from the human perspective excluding the people who are otherwise just as much part of the team as anyone else is definitely eyebrow raising.
I have worked for third party consulting companies for 5 years. Companies hire my company to do a job or issue guidance and then leave. If I am on the bench, I still get paid. I report status to the client company and they are ultimately responsible for signing off on work. But they don’t manage my work.
I’m not embedded into their team, we might embed them into our team. But at the end of the day, we are leading the projects.
Then you have staff augmentation “consultants” like you are referring to.
I saw both sides a few years ago when I was the dev lead for a company. We hired both staff augmentation “consultants” where we paid the contracting agency $90/hour and the end consultant got $60-$65 and we also paid the AWS consulting companies $160/hour and I have no idea what they got paid. But it was a lot more.
That’s what made me work on pivoting to cloud consulting in 2018. I didn’t know AWS when we hired the consultants.
Why is that ridiculous? Contractors are not employees, so why should they be invited to a give thanks party for employees? Become an employee if you want to partake.
Feelings of entitlement are wrong here. Decency though tells us to invite everyone.
How dare people have feelings right? A lot of contractors (like myself) are treated like employees who are easier to fire.
I understand the separation from a legal perspective, but at the same time I've developed relationships with the people I work with and enjoy working with them. Being entirely honest? It hurts being excluded from things and not everyone has the option to just "become an employee".
Christmas part is not special "give thanks to employees" party, it is more of end of a year party. It makes perfect sense to invite contractors. Even if it was "give thanks" party, contractors worked on projects.
I remember a work Christmas party attended by a contractor. The company was an sme and as usual we closed the office at mid-day and headed for a local restaurant to eat and socialise. The contractor as chatty and sociable, and seemed happy to be dining on the company's bill. Wine flowed.
Then at the stoke of 5pm, as we permies were discussing which pub to move on to, the contractor stood up, mumbled his thanks, and left. Billable hours over for the day.
Its caste. The cleaning lady is part of the company and its a horror that the dalit are dis-included from all company activities. The only actual reason is to divide and conquer and prevent them being part of any employee unionization.
I've been a consultant/contractor, less than 4 months in, and I still have been invited to (great) Christmas party, and even shared paid buses that took whole company and also given free accommodation.
Human decency is human decency, nothing more to that.
That's a manifestation of your specific environment and not a general rule. I guess it is the work of some overeager compliance department, because it is the kind of overreacting self-mutilation that happens if people do not understand a law and want to be absolutely sure (cf. GDPR).
[1] is a PDF that tax advisers and lawyers distribute to employers to check if freelancers are only ostensibly self-employed. The checklist at the end of the PDF is all you need if you are an employer. If you are a freelancer you must also check if you are employee-like and possibly file an application to be exempt. The PDF tells you when. Watch the 5/6 distribution of income (not law, but established judicature)!
> In Germany now there are laws in place for this, you get ridiculous stuff like as consultant you are not allowed to eat together with team mates from the employer because that is seen as bounding activities
AFAIK in Germany the model of using temporary agency staff (AÜG or "staff leasing") is now tightly regulated. It works for a limited time period and tries to guarantee some equitable conditions for temporary workers like fair treatment, equitable wages, and benefits, aligning with the protections afforded to permanent employees.
Consultancy has no such protections.
I have never heard of any laws that prohibit internal employees from socializing with the externals (consultants or AÜG), or eat together. Bonding can happen equally at the desk or the lunch table. And I haven't heard of any company or institution enforcing this. Legislating who one is allowed to eat with sounds crazy.
What many companies probably enforce is "no internal benefits for consultants", so the free company coffee, parking, canteen, or maybe even a desk/office are not available for the externals, and they have to look elsewhere. Or maybe some unwritten internal rules to discourage bonding.
You get that at many companies whose legal department is too worried that AÜG might somehow be triggered for them, or have a strong union that would rather see all consulting folks be gone, which I understand when placed in the shoes of internal folks.
Quite on point, for me it made me value the team, and no longer believe in whatever management tells about "we are family", "company values", or whatever else they feel like selling as the vision and company culture.
And this is why, eventually one gets tired of all reboots, and endless variants on Distrowatch, get a computer at BestBuy, Mediamarkt, Dixons, or whatever is the local chain, run GNU/Linux on a VM, and be done with it.
My favourite DBs are Oracle and SQL Server, and no FOSS religion is going to change my mind.
Too many folks lose on great technology because of hating the man, 70's hippie style.
And yes, I have used Postgres and MySQL and such.
It is similar to all the programming languages that have never moved beyond raw command line and basic editor tooling, only better nowadays, because of Microsoft (that they hate) making VSCode (driven by Eric Gamma of Eclipse fame), and LSP a common thing for all workloads.
>My favourite DBs are Oracle and SQL Server, and no FOSS religion is going to change my mind.
I mean even mentioning MySQL is better than Postgres in some areas is not even welcomed on most of the tech internet including on HN. MySQL reached 9.0 after so many years and its news doesn't even reached HN's front page.
>Too many folks lose on great technology because of hating the man, 70's hippie style......... It is similar to all the programming languages
And It is not just PL. It is pretty much all across tech spectrum, and even beyond tech. I am a tech enthusiasts, not an PL, Editor, DB enthusiasts. We should be able to admit Oracle and SQL Server are better now but we strive to make similar if not better DB that is open source.
Kind of, the real reason is that C with Classes was Bjarne Stroustoup's "Typescript for C", he wasn't going to use C bare bones after his Simula to BCPL downgrade experience.
However to be able to do that, C with Classes abstractions needed to perform just as well as writing raw C.
Fully spot on, that is why using Tcl with lots of native extensions might have been a great solution in the late 90's dotcom wave, we quickly validated with our rewrite into .NET, still beta at the time, the huge difference that having a JIT in the box makes.
Hence why afterwards I never been a fan of any language for deployment production without AOT or JIT tooling on the reference implementation.
At the time Mac Classic was relevant, PC still wasn't thar great in home computing, no one was bothering with this stuff in x86/PC.
We were still bothering with demoscene stuff in 8 bit home computers, and those of us busy with 16 bit home systems were focused on Atari and Amiga systems.
PC and x86 at home only took off, meany really taking off among demoscene and other home users, was when VGA and sound cards became part of a standard PC.
The Mac Classic was released in 1990, the Mac Classic II that is the subject of this article was released in 1991. At that time PCs with 286s and 386s were already common, and the 486 was just starting to gain marketshare at the high end. Most of the undocumented 8086 instructions had already been known for almost a decade; and the majority of those who knew were not demosceners. Many developers used Asm exclusively, and the "classic hacker mindset" was very much alive among them.
Depends on where in the globe one were and in my demoscene circles PCs only took off as interesting after Windows 95, folks using MS-DOS or Windows 3.x were mostly due to their parents family computer.
I think non-x86/non-PC-compatible home computers did remain relevant for a bit longer in Europe and Japan than in the US but by 1992 the writing must have been on the wall.
As someone that lived two years in Switzerland and still goes there regularly, don't forget how much things actually cost, the high value is artificial given how much even basic supermarkt good cost.
Including healthcare, vacation days, maternity leave, no calls after work or during vacations, not being on call unless paid for and is on the contract, unions,...
Maybe you just have no experience with Silicon Valley or just hate it for whatever reason, but the only thing in that list that doesn’t apply to SV is the unions… Not sure the point you’re making.
reply