321–330 of 345 posts
Earlier quoted context omitted.
The deprecated style rules have been ported by a new project: https://eslint.style/guide/why
Thanks for this. It completely escaped me and all I saw was the changelogs deprecating the very limited set of style rules I've used for years.
Earlier quoted context omitted.
Keep in mind as a freelancer you have to make about for $2.50 for every $1 a salaried person makes, as you're on the hook for 100% of taxes, health care, business expenses, etc.
Yeah, it's closer to 1.5x. Most companies budget total comp at 150% of salary.
Earlier quoted context omitted.
It should put more weight on the length that the author has original authored it as. So between "always break" and "always expand" there should be an area of "leave it however it already is".
Prettier needs to be consistent regardless of the original input. Otherwise it won’t really work well.
Earlier quoted context omitted.
I’ll second this that even in Canada, which has quite low tech pay, the lower end of quality dev work is $180/hr. Most of us managing contractors wouldn’t blink twice at $200/hr. Many of the bills are much higher.
where are you finding these rates at? i have rarely seen anything even passing $100/hr in canada, contract or not
It varies though, the market also exists for $80/hour java developers, which tend to be new grads
Contract Developers going to technical companies will earn more like $180+.
Earlier quoted context omitted.
Yeah, it's closer to 1.5x. Most companies budget total comp at 150% of salary.
Most? I can't think of a gig beyond maybe a couple of folks in a coworking space where I wouldn't be laughed out of the room with "just make it 150% of salary and we'll figure out the real number whenever". Virtually every company I've ever worked with budget the actual number, because they know how much the overhead cost is. There's a huge difference between "a number I use when asked 'ballpark how much a new hire i…
Earlier quoted context omitted.
That sounds about right. On the other hand it does mean that you are producing this kind of work for big FAANG companies you should expect to earn $80/hour. This is around the low end of a senior software engineer or the higher end of a junior software engineer.
I have heard of a database "engineer" paid $250 an hour to spend weeks creating what is basically a connection string to a database in a corporate virtual lan. The people paying him were never concerned about the cost, just how long it was taking. This was in Nebraska.
Earlier quoted context omitted.
how did you factor in when you can't work (sickness, holiday, increasing your skill, finding the next job etc)?
2088 potential work hours in a year Less 88 hours holiday Less 80 hours vacation Less 56 hours sick =1864 hours (these are federal guidelines under the Service Contract Act regs) 232/1864 is a base increase of 12.5% for PTO Payroll taxes, Medical, workers comp, etc add about 30% - though medical is flat so at higher wages like discussed here the % increase it represents goes down further I did not have to factor in i…
Earlier quoted context omitted.
>Great programmer who has the skill to answer this bounty get paid at least $200 an hour (extremely conservative estimate) Dang! What do you base this estimate on? The Rust aspect, or parsing aspect, or intersection of both?
Depends on the geography and/or whether the knowledge is highly specific. As a datapoint, the average Dutch contracting rates I see for IT development (think: Java, Swift, Kotlin) range somewhere from €75 - €150/h. Higher is possible, but then you're talking very specific expertise and typically shorter projects. I'm on the hiring side, this is a figure across some 20 external devs. I think it's representative of the…
Earlier quoted context omitted.
That's technically true, but extrememly rare to cause real problems (short of bad intent). It reminds me of people/teams enforcing braces on single-line ifs, because one might add another line someday, forget to add braces, and break the logic. Even when it happens, there should still be tests that catch this.
On the one hand, yes, there should be tests. On the other, `goto fail;` :P Also, adding braces from the start means that adding one new line of code is a one-line patch, instead of a four-line one - I do that for the same reason that I always put trailing commas on my array definitions
On the flipside, having three trivial early-return ifs at the beginning of a function will become 9 lines long with braces instead of 6 (or just 3, when doing single-line ifs). Very often, such cases never expand to multiple lines in the future.
Earlier quoted context omitted.
This is fine for a text diff, but I want my code review tool to show me something different. Separate problem, and the flaw here isn’t the diff, or the tool that produced the diff, rather the tool displaying it to me. Let me do whatever I want to my code and show me BOTH the visual (unimportant) and semantic differences.
Good point. Are there any code-semantics-aware diff tool out there though?
If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.