tetraodonpuffer

> Politicians should start Patreon campaigns to get livable wages from supporters and then just execute on what they stand for.

if somebody dangles 6-7 figure checks in front of many people, those people will find that their former concept of "livable wage" has suddenly been revised upwards.

If a politician is honest they can be honest within the lobbying framework or outside of it, the issue I think is making it so a honest politician with no access to extra funds can compete on issues against a well funded opponent (meaning getting people to know who they are without having to buy tons of ads): this can only happen if election campaigns are extremely regulated.

Doing that would mean things like no ads for anybody ever, only exposure via live debates, fixed identical travel schedule for everybody with access to the same rallies in terms of facilities etc. etc.

Even with all of this I am not sure it would work in the current social-media society, because as things stand now if you are well funded you could easily drown your opponent(s) on social media just by buying comments/influence and regulating those seems pretty much impossible (how do you distinguish between a genuine groundswell of support and a paid-for one?)

the response time of the rust team was extremely quick, great job!

2017-09-13 @ 19:19 - Justin sends mail to security@rust-lang.org about this

2017-09-13 @ 19:28 - response sent to Justin acknowledging the vulnerability

2017-09-13 @ 21:14 - a patch to crates.io was finished, all current tarballs verified not-malicious

I cannot believe how short sighted companies can be when it comes to these things, but I don't think it's malice per se, it's usually a variation of the person who makes the decision does not have to live with it and so doesn't have any incentive outside of spending as little as possible.

It's like how in many cases the desktops/monitors for developers come out of the IT budget, so the IT department tries to buy the crappiest things possible (24" single 1080p monitors, because they can't find anymore the 22" 900p they had before, 500 gig hard drives, etc.) because it does not impact them if developers are happy or not or are hampered by having to work with substandard tools.

In several past companies when we moved offices or had an office redesign, it was always up to the facilities department to deal with this, and developers were involved only at the very end when it was time to pick the seating and by that time all the design was locked, contractors hired and so on and so there was no way to change anything of significance anymore.

If I ever had a company I would make it a rule that any decision has to be made by the department / people affected by it. Other departments can offer support as needed, but I would never have IT control which hardware the developers get, or facilities decide for open office/cube height/chairs, or the CTO decide for the code review tool, etc. etc.

some companies do, one company I see openings for on the local job board puts something like "on your first day you will come in and go to your own private office" in all their ads. I have thought of working there just based on that...

if I am reading things right the radeon vega 56 is always faster (sometimes significantly more, like in koro) than an nvidia 1080 for rendering, that is quite surprising.

exactly the same, which means FaceID is not that much more secure unless as part of the authentication process you have to smile on cue or something

so does it mean that to unlock the phone I just have to knock you out and put some sunglasses on you?

doesn't the model S though also give you free access to superchargers (unlike the model 3 where you have to pay)? This should factor in the comparison if you live close to one and/or plan a lot of cross country trips where they are available

if the fire alarm is in a different room light would not work very well, with a strong enough smell no matter where you are in your dwelling you are going to notice it...

it also seems to adjust the spacing, I have used it with FiraCode and it seems to work correctly. Note my main font is DejaVu Sans, with this I just use the Fira Code symbols for the "ligatures"

note you can kinda use ligatures in emacs by doing something like

https://gist.github.com/pcstl/2d9b28a74d6f9254586c2d58d54590...

who is the gatekeeper in the company that is going to say "we don't need this"? Everybody has a vested interest in resume driven development, and these days "netflix/google/amazon do it, so we should too" seems to be like the good old "nobody got fired for buying IBM" (whether or not doing what a company at 100x your scale does makes sense)

thanks for chiming in and clarifying, best of luck with your hiring! as I was saying I definitely think it's a net positive for everybody to harness your interviewees' effort to improve open source packages that you care about as opposed to just wasting it on contrived exercises not benefiting anybody.

> do they really expect people to spend multiple working days on a job interview?

if you read the article they say their previous interviewing practice was homework that took about a week to do (described as "high effort") so it does seem they are looking for substantial contributions.

From the perspective of spending a week on an ad-hoc coding effort vs a week on an open source contribution I can definitely see the value, especially considering that it seems it's up to you what you do (you are submitting your "this is what I did" together with your application and not "I want to apply"/"fix these github issues") which also means you can decide the effort level and most important when you spend it.

Reading the article it seems nothing prevents you from working on this for 3-4 weekends and then applying, which seems completely reasonable and honestly not a bad way to go at it. It really seems a win-win-win: for the company, they get to evaluate you as a candidate, for you, you have a meaningful contribution for your resume even if the application doesn't work, and for the open source ecosystem as a whole, which gets some bugs fixed or features added

I mean, these days to interview you'd still spend several weekends refreshing algorithms and practicing so as long as this is the whole of the technical interview and not just the initial part plus a day of whiteboard algorithm quizzes it'd be a nice alternative.

I am less sure about the "cooking together" part of the hiring process, but if that's the culture they want to foster I guess that's their prerogative, on the other hand I do believe this should be stated up front and not be a surprise, given how not everybody would be willing or able to partecipate due to dietary restrictions and preferences.

couldn't we simply have crosswalks that have 3 buttons for short (bike) medium (normal walking) long (need extra time)? Seems like it would be cheaper and more accessible than an app.

how many pizza pies do you sell a night? and how much does a pizzaiolo make a night? I don't think the economics are there for automatization given how robotically complicated would be to actually make a thin crust wood fired pizza and how fast and consistently a trained pizzaiolo can do it in comparison.

I think any CI/CD system should be set up to also validate that any license used in the system has at least a month to go, and start complaining if not...

what are the exceptions? I thought that Mandelbrot was always guaranteed to be ok for this optimization (unlike, say, Julia)

and keep a set of text files for yourself where after learning to do it the right way you write it down. I find that especially with bash/command line things I don't have to solve the same problem often (which would help with remembering) but often enough to be annoying having to re-learn it all the time, so it really pays off to have some documentation to refer to. org-mode and vimwiki are quite good for that.

on windows I use WFC[1], which leverages the built-in firewall. Due to this though unlike LittleSnitch by the time you get a notification the connection has already been denied to the program, which can be an issue.

[1] https://www.binisoft.org/wfc.php

I find this use case interesting (linked from the comments in the ars article)

https://www.augmedix.com/

having the doctor wear google glass while a "remote scribe" takes notes for the doctor to sign off on later.

> you don't have to document things because people "just get it".

and then a year later when you have to figure out why something was done a certain way what do you do? or when some of the people that "were there" have left and nobody else remembers?

If all the discussions are written, there is no risk of forgetting anything: even working in an office I always send an email after a meeting or random chat to the person involved to document what we talked about, what was decided and why. I might also cc other people that should be kept in the loop, which is also something you cannot do if you just talk.

> Get rid of the unsafe factories and poor people won't be able to afford clothes anymore

poor people have always been able to afford clothes, it was called saving for a while to buy a good pair of pants and mending it for many years until it pretty much fell apart.

Poor people would not be able to afford new clothes all the time, sure, but clothes in general most certainly.

And let's not forget about thrift stores, go into any goodwill and you will be able to buy plenty of good quality extremely lightly used clothes for very little money.

API consumers might also not be very flexible when it comes to adapting to API changes: some might have developed fragile/inflexible code that will go up in flames if you even add a new field to an object (leading to support calls and escalations), this is why depending on your domain you might need very strict versioning requirements.

Some APIs will not change a version number even if new objects/fields are added, others will, it really depends by what space you are in and your customer needs and it should be taken into account when designing your API.

isn't this "third motivation" simply fear that if they don't perform they will be fired and their family would suffer from it?

Besides the books others have mentioned (peopleware and mythical man month should be required reading for all managers in my opinion), I would also suggest thinking about the following:

make sure you align rewards with the results you want: if you talk about code quality and so on, however you incentivize your execs/manager for "ship quickly and fix later", that's what will happen.

When interviewing all your managers/execs ask them "assume your team leads told you that feature X will take Y months to develop, and I told you that for business reasons we need to deliver it in Y * 0.85 months, what would you do" and hire/nohire depending on how you feel about their answer and how it maps to the books above.

Make sure that if you have a deadline you are flexible on deliverables, there is nothing worse as an engineer than being asked to estimate how long something will take, and then be told that the delivery is fixed anyways. At the same time if you ask for a ballpark estimate, don't then assume your engineers will hit that 99% of the time and bet significant marketing/sales dollars on it.

Some engineers will thrive in environments where customer-is-first and backwards-compatibility is king, where code quality and cleanness are prioritized and code written lives a long life. Other engineers will find that stifling and instead will thrive in a write-fast-and-throw-away environment, make sure you assign each type of engineer to the right teams.

And finally make sure that your company culture is aligned with what you want to achieve: some engineers will thrive in a private-offices/business-is-business environment, others instead will prefer a open-office/work-is-gamified place, hire accordingly.

I am surprised management issues are not making the list as a separate category (unless they are under (9)?) because things like your managers never having read the mythical man month, treating team members like replaceable cogs, or politics in general in my experience can be huge unhappiness generators...

I really enjoy reading books about re-living your life, I think the best two I have read are Replay by Ken Grimwood and the first fifteen lives of Harry August by Claire North, very recommended.

In terms of movies also About time incidentally explored some of the same concepts.

in many parts of the world zip codes are city-wide (regardless of city size), so that wouldn't help

fair enough, although I personally don't think that cutting bread and eating more potatoes is that big of a difference overall, it is a difference so hey, for all I know that might have influenced things. As I was saying above, n=1 after all.