[flagged]
Cucumber maintainer has been laid off
51–60 of 81 posts
Re: Cucumber maintainer has been laid off
#52I'm not suggesting that it is, but this sounds much more like a firing than a layoff. Pretty shitty way to do a layoff. This is the way you remove a potential problem, i.e., play it cool until the doors are locked, then full lock-out. That's very different from "Hey man sorry, but it's layoff season, as you know, so we're gonna pay you out for the next 4 weeks and you can keep your coursera subscription."
Re: Cucumber maintainer has been laid off
#53I have used Cucumber in various projects, but haven't yet had the pleasure of seeing it all work out. - No one wanted to "collaborate", or check a "documentation" based on the Cucumber code . Yes, it's code, it lives in an IDE, in git, and non-technical folks just generally don't deal with that world. No one in my projects ever even brought such an idea up. Non-technical folks looked at our Cucumber code as in "what…
We tried it once and the semi-tech SMEs had no desire to write cucumber code so it ended up being the developers who hated writing in a second language. No real benefit.
I don't mind developers writing the Gherkhin as long as the SMEs can read and sign off on the Gherkhin. They won't read a unit test for sure.
Re: Cucumber maintainer has been laid off
#54I'm not suggesting that it is, but this sounds much more like a firing than a layoff. Pretty shitty way to do a layoff. This is the way you remove a potential problem, i.e., play it cool until the doors are locked, then full lock-out. That's very different from "Hey man sorry, but it's layoff season, as you know, so we're gonna pay you out for the next 4 weeks and you can keep your coursera subscription."
Been there. I was laid off, the same (shitty) way, returning from vacation on March 29 2009.
Took me almost a year to stand on my feet again.
Life is Good!
Re: Cucumber maintainer has been laid off
#55Earlier quoted context omitted.
This is why we need better tools which will give benefits for the added complexity. If you need to create both the feature files AND the code, it's just complexity with little benefits. But frameworks like https://github.com/karatelabs/karate or https://github.com/Endava/cats are hiding this complexity and remove the code layer entirely. Which, in my view, this is where you need to be in 2023, particularly for API te…
I'd completely disagree. Not necessarily for cats, which I wasn't previously aware of, but in my experience there's no benefit to having karate in the mix.
Why would you say that? Majority of code is repetitive. Why still focus on writing it for every project? I agree that you cannot have 100% of tests without actual code, but a significant percentage can just be feature files only.
Re: Cucumber maintainer has been laid off
#56I have used Cucumber in various projects, but haven't yet had the pleasure of seeing it all work out. - No one wanted to "collaborate", or check a "documentation" based on the Cucumber code . Yes, it's code, it lives in an IDE, in git, and non-technical folks just generally don't deal with that world. No one in my projects ever even brought such an idea up. Non-technical folks looked at our Cucumber code as in "what…
Non-technical folks write complete IT systems in the nightmarish programming language of Excel macros. I think the language used language isn't the main blocker here.
If I’m told to build a report or form collection for a product.
I always tell them to go build it in excel first. Than it to hand me. Sometimes I build it out in excel. 100% everytime they change everything about it several times over, but I can make all the changes requested in minutes instead of hours, days or weeks.
Implementing a working excel document in a modern language is trivial.
Re: Cucumber maintainer has been laid off
#57I'm not suggesting that it is, but this sounds much more like a firing than a layoff. Pretty shitty way to do a layoff. This is the way you remove a potential problem, i.e., play it cool until the doors are locked, then full lock-out. That's very different from "Hey man sorry, but it's layoff season, as you know, so we're gonna pay you out for the next 4 weeks and you can keep your coursera subscription."
Been there. I was laid off, the same (shitty) way, returning from vacation on March 29 2009. Took me almost a year to stand on my feet again. Life is Good!
2009, one of the great vintages.
I feel you. There've been some wild swings in the past 20 years.
Re: Cucumber maintainer has been laid off
#58I'm not suggesting that it is, but this sounds much more like a firing than a layoff. Pretty shitty way to do a layoff. This is the way you remove a potential problem, i.e., play it cool until the doors are locked, then full lock-out. That's very different from "Hey man sorry, but it's layoff season, as you know, so we're gonna pay you out for the next 4 weeks and you can keep your coursera subscription."
The difference is sort of meaningless. What matters is if you are getting severance or unemployment, and if you can get a recommendation. If they are going to fire you for invidual performance, youd think they would put you on a pip, but some companies will just wait and lay you off.
But the two can be similar in that if you are valuable you won't get fired or laid off, unless the company is in serious trouble.
Sometimes you are just on the wrong project. It is good to be generally aware of your projects value if you want to keep your job.
Cucumber, IMO, died like 8+ years ago and never really made sense. It was useful for a team to define requirements and then see the progress to implementing them, but Gherkin was a sticking point and integration tests are hard to get/keep working, esp with javascript apps that are now so popular. The fact that someone would pay a OSS maintainer up til now seems like a crazy waste of money.
Re: Cucumber maintainer has been laid off
#59The American way of firing people with no notice and cutting off their logins instantly is so strange. Is saving a tiny bit of money that much more important than a smooth handover? Or are employees just not willing to work their notice periods? It sounds like in this case it's actively going to hurt the business.
Usually if it’s a layoff (without cause) and the employee does not have special powers (officer of company) a long notice is given to support a transition. A compensation package which requires signing a contract is the incentive for the employee to cooperate.
This seems incorrect. I was recently laid off and there was 0 notice.
Re: Cucumber maintainer has been laid off
#60The American way of firing people with no notice and cutting off their logins instantly is so strange. Is saving a tiny bit of money that much more important than a smooth handover? Or are employees just not willing to work their notice periods? It sounds like in this case it's actively going to hurt the business.
Companies just want a clean break. In cases where they really need you to do a hand off, you will get a transition period. I've had that happen to me, and it's a weird feeling. I don't think its great for productivity or morale, and is more common when you are shutting an entire division down.