Details
Joined devRant on 4/3/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I dunno, it’s easy to have that perception if you read US tech news but
My experience (in Europe) is that we had more people than before being allowed to move to entirely different places and become remote. Mostly senior though (we would not hire a junior dev who wanted to be remote)
Any my college friends who call themselves digital nomads are still travelling around as they always have
- their notion is that it is easy to get a short time consultant gig as a remote worker - but some companies would want you to attend some office meetings in person if you want a long term job -
It is kind of ironic when Linux users bash Windows and Mac users saying they don’t know how much time they are wasting on a subpar OS
And when asked about how they save time on Linux some go ”Ehrm.. I mostly spend time reinstalling it. i switch distros every 3 weeks” -
Gotta be a downer here but tons of these services have existed even before the AI boom - google ”yoda translator”
But hey - just because something exists doesn’t mean you can’t be successful with the same concept in a different package.
This would be one of the easiest things to build using any language based api - as you’d just have to enter a user prompt plus a set of instructions like ”say it like Yoda” -
@Demolishun I feel the same. Sometimes. But there can still be extreme limits. Like having text rendered at 800 words per line when the intent was 60.
Or tall images intended for mobible end up taking "4 full screens" on an ultrawide monitor - so you can't even see what the heck the image is supposed to be as you can only see 25% of it at a time -
I feel the same but to be honest
It’s irregular that a ”normal employee” would be paid a percentage of profits.
Unless you were part of a startup with stock options as part of your salary.
To some extent I would feel it would be unfair if me and another dev made a vast difference based on one of us working for a company that struck gold -
This post makes it seem like the company would’ve hired hundreds of devs if they were good
Is it confirmed that only 3/8 passed the simple test? Or did they just eliminate 5/8 because the goal was to reach 3 final candidates? -
Both?
-
To some extent: they might try to be helpful but they forget stuff
I struggled for years to get designers to stop thinking DesktopFirst and do a MobileFirst design - but when they got om board they went too far and had to remind them ultrawide monitors exist and desktop content widths perhaps should be limited. They thought they were just being helpful by ”simplifying the design to always be full width”
Once they saw the issue they got it -
Show them a mockup film of a prototype site on an ultrawide desktop monitor where the image is ”taller than one full screen” and how silly it looks when you scroll by it
-
To me - the FAANG definition - requires a huuuge company.
If you’re just looking for WLB, benefits, and high barrier - but you don’t care about the fame or size of the company:
I think there are plenty of smaller companies - a lot of consultant firms.
When I worked for a large dev consultant firm that declined I saw a lot of the best and most experienced people leave to join smaller firms where the 3 values you mention were part of their core values
But these were the opposite of FAANG; their selling point was like ”We only have 30 employees but they are excellent” -
Serious answer:
The Edge sits between the browser and your origin server
Edge is often like a CDN (like Cloudflare, AWS, Akamai, Fastly)
When browser requests your site - The Edge server responds first - ideally 90% of the requests can restult in a cached response where no traffic is even sent to your origin server, allowing you to have a very low server load despite millions of requests
”Edge computing” or ”Edge workers” would mean something unique like a username might be injected into a cached response - without needing to call your origin server -
To play devil’s advocate 😈
It is common that there is no detailed document called ”company policy” with all the rules. I do not know of such a document at my company. But over the years some employees have built a perception of what is against company policy - based on stuff like statements from the high ranking managers.
One example from my company: a few years ago in my country - some competitor accidentally posted news like ”The President is Dead” in a CMS they thought was a staging CMS. And some personal data was leaked because someone used a public sharing service to quickly send info to a stressed customer.
Our CEO commented on these incidents and said we should never do that. We stick by it - Yet I’m not aware of any ”company policy document”
PS: I’m sure your request was nothing like that - so my post will seem
dumb. But just saying. -
There are several articles trying to statistically explain the high amount of Israel votes
The major theory is that there weren’t many standout songs - so The Palestine supporters vote was spread among many countries. While the Israel-supporters all voted for the same.
And the theory is some were annoyed by the booing of Israel and voted for that artist in sympathy -
You can’t vote for your own country so the UK population in regards to the UK vote is irrelevant
-
I get the rage
But did anyone else get 5/5?
People can have very different ideas about grades.
Just talked to some people about how they rate restaurants and one said ”if there’s no problem my default is 5/5. The other day I was a place that was rude and gave me the wrong food. So I just gave it 4/5”.
The other said ”if it’s solid it’s 3/5. Most local places here are not above 3/5. To get 4/5 I want something special, a unique experience. 5/5 means it’s one of the best ever” -
Never really thought of em to be totally different like that. I guess it’s true.
But to me if I talk ”functional programming” it would be something like Haskell or F#. Or If I talk ”OOP” it would be a large custom business layer.
It is possible - to use both react and vue mostly as declarative programming -
I can imagine that must suck. 😓
Both for you and for the person hearing it.
Cause if I was the touchy type - I would feel so awkward if I thought I was bonding with someone - and tried to gave em a pat on the back or a shake or something - and then heard ”I hate physical contact” -
I agree it seem rude.
But it has to be said: this is part of the reason why some companies are reluctant to hire employees that don’t speak the native language - for a company in Iceland this is a non-issue as long as everyone speaks Icelandic - as soon as they hire a few people that don’t this becomes a potential concern
There might be ideas of hiring english speaking devs are desperate to be hired - but this is a concern. Companies are afraid spontaneous conversations will be lost if everyone has to speak english -
If you feel social lunches drain your energy - it could just be that 9/10 of your coworkers are like that - but if you keep trying you might find 1/10 that suits you.
It seems unthinkable at first. But I’ve had experiences like that. I hated certain types of workshops lead by designers - went thru 5 lead designers in my company and started declining all workshops. Until I the 6th one which was amazing and changed my mind entirely. -
For me - variation is key.
I work from home at least 1 day per week and will eat alone.
Most days I go out of the office building with a group to eat at nearby restaurants.
Some days I eat in the office cafeteria. -
I agree it sounds like a low effort job
But I sometimes view this a a doctor health check: if the doc says nothing is wrong - was it a waste? Nah, sometimes you want a pro to assess if there are any problems or not.
Like if you run a Lighthouse check on your site and get a perfect score - the check was worth it even if it concluded there’s no relevant change necessary
But yeah - sounds like a bad effort. Cause branding and design is usually something designers wanna change according to trends or experiments - every X years - even if there’s nothing wrong with it -
If I was you - I’d be honest and tell them up front you don’t wanna work with WP. Then maybe ask to speak to a member of the dev team - to get a sense of what they really spend most of their time on in daily work.
PM:s can have an overview of a large team - but can be really poor at describing where most work is done and how it is distributed.
For example I worked in a team of 7 devs where 2 maintained a soon-to-be-obsolete dotnet site and 5 worked on a nodeJS site and once heard them say ”It’s a mix of dotnet and js” and I had to interrupt to correct that dotnet was entirely irrelevant for any new hire -
@bad-practice Probably a good thing. When you’re job hunting and you feel bad vibes from a company you sometimes wanna keep them around as option B but keep searching. That can be difficult though. Some companies are so urgent once they make a decision they will go ”you’re accepted! Let’s negotiate tomorrow” and then it becomes stressful to say ”I’m not sure”
If youre undecisive - that can stress you out for a few days -
I would feel uninterested in a job if the interviewer was dead serious
Unless the interviewer was an external recruiter I would try not to care - and wait until I met someone from the actual company -
If you don’t leave - at least start job scouting. There are many companies who really care about Work Life Balance.
(To the point where some want to work more - but are encouraged to go chill out) -
This will surely influence many other european nations - but it might take a very long time.
I think many types of national laws are very specific to the political tradition of that country, and to a large extent immune to influence from other countries.
2 examples: In Sweden, Norway and maybe Finland you cannot sell beer above 3.5% in supermarkets, only from a govt store with limited hours. This has persisted for decades despite most other european countries not doing it that ay.
Example2: Norway. Pro boxing was banned from 1982-2016 because they did not like sports that encouraged people to knock each other out. And there's a law that prevent large stores from being open on Sundays. Even large grocery stores are closed on sundays (with a small amount of exceptions) -
@Lensflare Yeah. I think in many cases it is willful ignorance. Or basically just a confession that the deadline dates do not really matter - it's just a part of bureaucracy that they need to insert some date into a Roadmap for their next presentation. And it doesn't really matter if that deadline date is missed. The presentation just has to be written.
A classic example that comes to mind is whenever it's close to christmas a bunch of deadlines will be set to "week before christmas" - and they will not be updated even if conditions change.
(But sometimes they are nice enough to say "Either we make the deadline or we don't. We'll see") -
Follow up: sometimes I prefer tickets with 'fuzzy' requirements.
If a ticket is the top priority and "should be worked on until it's done" I'm fine with it being poorly defined and the team can just say "Let's just have a dev, a designer start working on this and talk to a stakeholder to define where it needs to go"
Because I dislike all the meta-work around backlog refinements, pre-planning tickets, all the guesstimates. I love just "work on this until it's done" -
From what I hear: some stakeholders are fully aware that they ask for arbitrary deadlines - but they do it intentionally to start a discussion - assuming that this will ”get the discussion going faster” and force the dev team to think about it and respond saying if it is not possible and why - ans suggest a new date
-
In these situations I find it helpful to ask if the team has defined a strict policy that tickets should be properly defined before they are placed in a sprint.
I have been in a team where all us devs were under the impression that this was the case, but stakeholders thought that requirements in a ticket were just some "initial ideas" that would "probably have to be revisited/revised/rewritten whenever a sprints starts and someone actually starts looking into the ticket in detail"
After this we had a discussion and started using 2 different labels for tickets: a) well-defined b) fuzzy