101–110 of 124 posts
I just tried out the AWS offering for CI/CD (CodePipeline/CodeBuild) and was disappointed with time-from-commit-to-deploy (to ECS, although it's the launch/build time I'm primarily concerned with here). It appears to waste 1-3 minutes on just queueing and provisioning a new VM to do the build. It's highly variable, too. The main tradeoff (if the cost difference is insignificant) between this and a third party service…
Earlier quoted context omitted.
Gitlab advocates for paying local salaries. That’s actually against my “philosophy“ as you put it, as it is against my direct interest, being a non-US based software developer. Their way to promote remote work is, ironically, hurtful to my prospects as a remote worker.
IMO it's better for our long-term interest if companies can pay what the market will bear. For now splitting the surplus is win-win; as remote work takes off then there wil be more competition and salaries will rise. Growing the pie is better than asking SV employers to overpay on some point of principle.
That’s just silly
Earlier quoted context omitted.
Gitlab advocates for paying local salaries. That’s actually against my “philosophy“ as you put it, as it is against my direct interest, being a non-US based software developer. Their way to promote remote work is, ironically, hurtful to my prospects as a remote worker.
That's fine. I'm not trying to convince anyone that Gitlab is the messiah or anything. Someone just asked me why I align more philosophically with Gitlab than Github, so I explained what appeals to me personally. If they don't align with your philosophy, that's cool too. You get to choose how that affects your choice of VCS/CI provider.
Earlier quoted context omitted.
This seems like a variation on the fixed pie fallacy. It's absolutely in the general interest for more people to get paid more. How do you expect poorer markets to catch up with richer ones if you believe that it is bad for people in such markets to get paid more? Nonsense.
It's much easier to catch up if you can compete on price to start with. Why would a company take a chance on a developer in a new location if they've got to pay just as much? Once there's a critical mass of employers hiring in my location, competition will raise salaries up to parity, but sharing the surplus is what incentivises that competition in the first place.
The pandemic made a lot of people realize they can hire remotely and be fine. Why should I share the surplus with the company? I am a good developer and I will negotiate to get a better pay. Why wouldn’t I?
Earlier quoted context omitted.
This seems like a variation on the fixed pie fallacy. It's absolutely in the general interest for more people to get paid more. How do you expect poorer markets to catch up with richer ones if you believe that it is bad for people in such markets to get paid more? Nonsense.
It's much easier to catch up if you can compete on price to start with. Why would a company take a chance on a developer in a new location if they've got to pay just as much? Once there's a critical mass of employers hiring in my location, competition will raise salaries up to parity, but sharing the surplus is what incentivises that competition in the first place.
They're not taking a chance on location. Location is irrelevant to the job.
How can a CI-service not support ANY GIT source? All this garbage surrounding GIT is just baffling.
Earlier quoted context omitted.
Related, GitHub has had 'use more powerful hosted runners' in the pipeline for over 2 years[0]. This issue replaced another now-deleted issue[1] from July 2020. Really disappointing, as I've had to resort to using `az vm start` -> run -> `az vm deallocate` to use an on-demand powerful runner. 0: https://github.com/github/roadmap/issues/161 1: https://github.com/github/roadmap/issues/95 (note: added `ga` `ae` and remo…
I'm a bit biased as one of the founders of BuildJet, but we solve this exact issue. BuildJet for GitHub Actions, plugs elegantly into GitHub Actions. With 1-line change in your config, you get 2x speed for half of GitHub's price. Check it out @ https://buildjet.com/for-github-actions
Earlier quoted context omitted.
It's much easier to catch up if you can compete on price to start with. Why would a company take a chance on a developer in a new location if they've got to pay just as much? Once there's a critical mass of employers hiring in my location, competition will raise salaries up to parity, but sharing the surplus is what incentivises that competition in the first place.
> Why would a company take a chance on a developer in a new location if they've got to pay just as much? They're not taking a chance on location. Location is irrelevant to the job.
The timezone alone may rule out a location.
Culture is closely aligned with location, and every company cares about "cultural fit" (while pledging to support diversity, of course) for better or worse.
Misaligned holidays, internet connection quality, even power supply disruptions... and so many things are directly affected by location.
How can someone think location is irrelevant?!?!
Earlier quoted context omitted.
> Why would a company take a chance on a developer in a new location if they've got to pay just as much? They're not taking a chance on location. Location is irrelevant to the job.
Patently untrue. Setting up accounting in a new country may be a huge effort for the company. The timezone alone may rule out a location. Culture is closely aligned with location, and every company cares about "cultural fit" (while pledging to support diversity, of course) for better or worse. Misaligned holidays, internet connection quality, even power supply disruptions... and so many things are directly affected b…
Earlier quoted context omitted.
Patently untrue. Setting up accounting in a new country may be a huge effort for the company. The timezone alone may rule out a location. Culture is closely aligned with location, and every company cares about "cultural fit" (while pledging to support diversity, of course) for better or worse. Misaligned holidays, internet connection quality, even power supply disruptions... and so many things are directly affected b…
That's all true but besides the point. Paying a developer less because they have bad Internet connection quality, lack availability or because they incur more administrative costs makes sense. Those are all things that can affect their work performance or cost. Paying a developer based on their cost of living or based on what their neighbors are earning is nonsense.
I agree it "looks" like nonsense... but it's not. It's reality. Different countries, even neighbouring countries, can have completely different salaries while doing the same thing... and things can cost completely differently too... Just check the border between the USA and Mexico.