They don't explain how, they never do
Do they know something about prime number mathematics that the rest of the world doesn't?
27 posts • joined 16 Jun 2020
I enjoyed learning Flutter and Dart for fun hacky-home projects (it is cool) and then wondered what the commercial drawbacks might be - the first one I always check is developers. Are there any even remotely nearby. The answer was: no. I could find Dart/Flutter agencies who would "build a front end for your backend" but recruitment seemed to be a dead end. If they keep pouring money into it, perhaps it will pick up over time.
Of the monoliths I've worked on, I think most of them looked like: static front end that talks to an API which wraps business logic around a database. None of them used features of the OS. They could be hosted just about anywhere (framework permitting). However, having used lambda, I felt that the debug toolchain wasn't there but watching it closely as it could be a good fit for my current role in the future.
"The agency recognized that Microsoft had already addressed their concerns and did not require any changes to our hiring practices"
13.4% US population in 2020 (US Census) is black, MS demographic is 3.5% (MS 2019 diversity report).
They've already addressed their concerns?
"In the US, we are seeing incremental but slow progress in African American/Black representation"
I was wondering what the experience will be - an update to the app where users in the US won't be allowed to access their content? Will they be allowed to download their videos? Is the service going to be paused or data deleted? If so, when? Had a quick Google and could only find hysteria.
Statistics is about understanding the relationship between input variables. Artificial Intelligence (be it evolutionary computing, neural networks, learning classifier systems or a mix thereof) are about matching input to output. For example: a neural network cannot tell you what the relationship is between your height and weight but it can guess your BMI.
It's a different thing. Machine learning algorithms aren't that new but it's not statistics.
In our specific case, it's turned out cheaper in total cost. We grow/shrink as needed, embrace monitoring, patching agents and I am able to wear infrastructure wonk hat along with others in a small company. Not having on-prem tin makes ISO27001 cheaper to maintain and I've not need to visit an office since February. It was jarring having to learn all the new nomenclature (oh! security groups ARE virtual firewalls etc), they change the service underneath (although that did happen with software updates for on-prem too), you might accidentally configure something that's expensive and I find cost tracking a necessary tedium. Your mileage might vary.
FYI the Cloud Act applies in the UK only because the US/UK signed an agreement last year. Otherwise it would have broken GDPR. https://www.insideprivacy.com/surveillance-law-enforcement-access/10167/#:~:text=It%20obligates%20each%20Party%20to,jurisdiction%20of%20the%20other%20Party.
Language is indeed power and politics... but it's also so much more. When you think and form ideas, language helps structure those ideas. If a language has a particular concept then it's easier to form and communicate new ideas around that concept. I fear that as we lose languages, we lose those concepts that are unique to the cultures that spawned them.
I'm a big fan of Scots, it's more lyrical than English and allows for terse, humorous exchanges that lose their bite if done in English.
We don't write code on a whiteboard during our day to day, so why ask them in an interview?
I know that they are popular with Goomicropplebook but I don't think they are effective. Much better to get someone to bring some of their code with them and get them to talk through it; explain how it works, what they would improve it, ask them how a feature might be implemented. That's more like the real world rather than this nonsense about whiteboard coding.
As others have suggested, I like to have paper or a whiteboard at hand so that the candidate can explain things by drawing. That's not the same as writing up on a board with a pen.
The whole whiteboard coding smacks of quasi-faux-academia. "Look how cutting edge we are: algorithms on a whiteboard; just like real science". Yes, I did that in academia but there tended to be two or more collaborating on a problem, not 3 judging another for a job role. And it was never much code, lots of diagrams, some maths and doodles.
This will sink down in the comments because it's from someone who uses .NET every day and is content to do so.
I've been building web for 20 years in different forms and I do like C# as a language. Where I need object models, I have them. Where I need dynamics, I have them. Where I want a more functional style, I can do that too. If someone wants me to integrate with a legacy telnet client than I can interop if need be. I'm more productive than code I've written in Typescript/Node or Python or PHP or Perl. I can choose whatever database I want, I swapped MSSQL to Postgres with very little faff and I've used Raven, Couch and Mongo too. I've deployed to Linux as well as Windows, although I'd prefer Linux for future work Whatever fits the need. In my spare time I get to write Unity games in the same language, which is nice.
My bug bear has been with their naming. .NET is a stupid name, always was. In the early days googling for a .NET thing would throw up domains more often than not. .NET Core should have been given a new name that was nothing like .NET because it is a new product. There is no direct upgrade path from framework to core unless you're lucky to use supported libraries with supported features. They should have introduced it as a new cross-platform system rather than hanging onto the old name. With .NET Standard thrown into the mix, it's added a confusion that would rightly put people off.
Structural racism, ableism, gender equality is "death by a thousand cuts". No-one in those communities will be directly offended by the use of "blackhat" or "whitehat". However, they are small drips that add up. The government isn't banning them. Companies aren't firing people for using the old terms. They're just trying to gently change the language over time. And because society is built upon the way it communicates, thousands of tiny changes like that add up.
Language evolves over time, especially quickly in tech and although I understand those that extrapolate to a dark future, cool heads will prevail.
Biting the hand that feeds IT © 1998–2020