Git is a program your computer runs to have a single folder have source control. It does all the hashing and commit chaining that you’re used to, branches, that sort of thing.
But if you want it to be on more than one computer, you need to do this complicated “Bare” repository setup on a server computer to do the “git push” stuff you’re used to.
Most people, being too lazy to learn bare repositories and the general sysadmin necessary to host a git server themselves, instead just use Microsoft’s Github which is a web interface for the server use of git the program.
Microsoft then proceeded with their classic mantra of “Embrace, Extend, Extinguish” and started slapping on more and more features that are incompatible with any other git hosting service: actions, CI, their web VSCode instances, etc. That’s all in GitHub too. But it’s all just web interface for git the open source program, at the end of the day.
Just a few comments on this. Most people aren’t “lazy”, they just understand that the effort to run a bare repository is greater than basically any other solution. Also your incompatible features list implies that other git repo sites (gitlab, codecommit, bitbucket, etc) don’t have their own form of proprietary stuff that you have to learn. In fact the newest version of gitlab actually changes their web ide into vscode web, because of the obvious, it is much better than their old ide.
I like shitting on M$FT as much as the next bloke but if you believe Github started being evil when Microsoft entered the picture then your memory is pretty awful.
From it’s inception github pushed proprietary tagging and issue numbers that have no meaning outside their platform and a difficult export process to trap projects - especially commercial ones - on their platform.
I remember moving a project from github to gitlab years ago (before MS) and the process to move all the non-git data from github was just as easy as moving the git repo itself. Thanks to gitlab’s efforts perhaps, but I didn’t expect github to have made it difficult for them based on the experience I ended up having.
I was being diplomatic because I was uncertain how people felt about the issue and PR tracking, considering how Bitbucket and GitLab replicate it. Felt simpler to focus on the since-M$ft egregious steps.
“Alright, but you better be outside of a properly locked up and OSHA-compliant castle with the princess by the time I get back, or I’m not compiling”
And then you do that, but you miss a smoldering ember from one of the castles torches, and everything including the horse and princess catches fire. Next time, pick an escape plan that only requires unsafe for the drawbridge.
There’s a totally safe way to do it too, I guess, but it involves building a series of replacement castles, and it’s also totally ugly and sinfully slow.
There’s some truth to it. I’ve seen devs not clarify something from the designs with other stakeholders due to lack of social skills. You end up with something they implemented to the spec, but makes no sense it reality.
The go community is strongly opinionated in unique ways. For example, using libraries is generally frowned upon. You either use something included in the language itself (standard library) or copy/paste the code you wrote in another project. There’s also advocacy for shorter variable names which generally seems counter to the normal “write descriptive variable name” mantra.
All in all, I hope the ideas / opinions came from a good place and then some people took them as black & white rules. But they also come off as one or two people’s pet peeves who got to build a language around them.
I think the mention of fintech in the text makes an implication of online store of some sort, where I could see it being profitable because it’s a lot more work to be able to generate listings and accept payment and shipping information.
That was never in question. Online payment portals are Fintech. You don’t have to work at IBM to be in Fintech, it includes the entire process built on top of their platform as well.
I’m saying that the mention of Fintech in the First Case would IMPLY that the WebDev also deals with Fintech. If both devs have comparable skillsets then it makes sense to compare their pay rates.
That’s crazy. If you have the skills don’t under value yourself. Don’t be afraid to walk away from an offer. Never tell a potential employer your current salary and never give them a number if they ask in interviews. Ask what their range is as a response and if that matches your number, proceed. Then negotiate for the max of their range. If you get to that point, they already want you, so you have the upper hand in negotiation.
Doubtful, I was just joking about how it’s an older language that has become rare
Probably a few CS programs offer courses in it, if nothing else because it’s historically important. And I’m sure one could teach it to themself via books and documentation
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.