Not only that, but it's also fairly potent, allowing you to pass variables from one request to another, transform response, inject .env vars etc.
If all of your team is using Jetbrains products, you can also add the http files to the version control so everyone could have the requests ready to use.
Not using the mobile version that much, so I can't give feedback on that, but the desktop player is getting worse and worse for the past few years: searching, discovering (by browsing), library/playlist management etc.
It's like the Spotify guys are not even using Spotify anymore :)
@retrocryptid: probably you're looking only at the images from the article, but it seems it's a full keyboard. And it's symetrical AND programable so you can customize it as you wish.
You can turn on the autocomplete-by-enter by openening dev tools -> settings (f1) -> preferences -> console -> „accept autocomplete suggestion on Enter”
The short version: I was working on and off on upwork for the past... 10 years or so (since they were called elance). Didn't had too many projects (less than 20) and only applying there only for very small gigs, when I had some breaks from my regular clients (a couple of times per year).
Some years ago, one of my client went out of business and I wanted to give upwork a serious go, as I already had _some_ projects there, the account was verified and such.
Start applying on jobs that matched my skill set, asking for my regular hourly rate (hence the audacity). Looking backward, my requested rate wasn't even that high, but that's a story for another time. :)
Dunno how they work now, but back then they had a certain amount of credits every month that you could use to apply to jobs. IIRC, you could apply to 10-15 jobs every month with those credits.
Which I did.
I applied to about ten jobs, on most didn't had any replies from the client (they either closed the job or picked someone else), but the gist is that I didn't get any job.
One day, I get an email where the gist was: you weren't able to get any clients with your credits, so we don't need you. Same as OP, tried to contact them, but the decision was final and that's that. Fortunately, I didn't loose anything but some internet points :)
You go through an addmission process that's pretty much similar to an employement process (several interviews, technical interviews, tests etc).
After you get in, most of the jobs you get are strongly limited to your particular skill (so you won't be able to see what coding jobs are available if you're a designer).
Then, the customer aquisition process is slightly different, as you don't talk straight to the client while you're „bidding”, but with a recruiter, who deals with selecting the right candidate for a job.
Finally, for most of the jobs you don't even have to _apply_, as recruiters constantly send you messages for potential jobs.
Now, upwork & freelancer are mostly a race to the bottom; I personally got banned from upwork for having the audacity to apply to jobs and not winning any (because I didn't wanted to work for peanuts).
Depends _very_ much on how you define productivity.
Is your job moderating a big forum? Then no, you can't really bost anything.
Is your job writing about various topics? If this requires documentation, with a bit preparation before hand, sure, you can be super productive.
Is your job coding? Offline manuals will get you a long way (assuming you don't depend very much on 3rd parties like APIs or package managers).
Now, if we exclude the 1st point, yes, you can, here is how:
1. Get a good pair of headphones. Not necessary with active noise cancelling, but ones that do a good isolation of environment.
2. Download all the tools you will need: manuals, documentations, libraries and whatnot. (back in the day there were lots of site downloaders like httptrack)
3. Download some sounds. Be it music, white noise or whatever suits you.
4. Start doing stuff.
Hint: if this is one-time, long trip, you could use that time to read a book to elevate your skills ;)
Optional implies that user do something very intentional to disable JS.
But there are some cases where things go south without user direct intervention. Just to name a few:
- some edge bug that will render your whole site as a gorgeous white page
- some browser extension that mess up with a site
- some network configuration/condition that prevent JS loading correctly (think of a broken DNS)
Then you don't have too much of a choice: gitlab all the way :)
We ran an gitlab instance for about eight years and it worked flawlesly[1] for a team of ~20, with quite a few active repos (i.e. constantly pushing), some of them being generously large, running several pipelines on most of them.
PS: gitorious was aquired by gitlab, not gitolite. My bad.
[1]: once we pumped up _LOT_ of RAM into it that is
You may want to give more details about your usecase: do you need _only_ git hosting or other features too (e.g. issue tracker, CI/CD pipelines)? How many users will use this setup? Do you have a dedicated machine or you run it locally (e.g. in a docker container?? Hosting locally or in cloud?
IIRC Gitolite was aquired by Gitlab a while back, Gitweb is not really a git hosting, it's more like a web view of your `git log`
Gitlab needs at least a couple of gigs of RAM to run well, double/triple that if you need CI/CD.
You literally can train anyone, as non-tech as possible, to crimp 8 wires with a $5 tool in 5-10 minutes.