Uses JEV to do something that's one line of code. Also, "leftpad" was a useless package from years ago that many important packages used instead of writing the code themselves. Its outage at some point broke a lot of packages.
2,632 karma · joined March 19, 2011
All opinions are my own and do not represent my employer.
meet.hn/city/it-Trento
Socials: - github.com/sklivvz
---
- some are completely and utterly incompetent (they can't write a line of code at all)
- some write some code but it's just bad quality or they are incredibly slow
- some lack basic notions we require (e.g. don't know what a byte is)
- some blatantly cheat with ChatGPT or other tools
- some rage quit ("how dare you ask me to code")
- some fall into deep rabbit holes, overthink everything and make a mess
On the other hand the people that pass:
- all of them solve this in half the time we give
- even if they are nervous
In other words there's a chasm between the hires and no hires. Assuming that this interview only measures nervousness is a completely wrong notion.
BTW if you are interested in helping us transitioning the world from fossil to renewables, we are hiring: https://jobs.intellisync.it/
It's not only the sound, it's the sound, the bounce, the response to different strengths, the smell, the color. Humans are multimodal, machines are not, yet.
The moment we have a Michelin star level robot cook, then we can start thinking about automating this kind of stuff. For now, we have better results with humans!
Italians have absolutely zero problems replacing manual processes with technology. Creating each wheel is more science than art, everything is done in highly sterilized environments with exact temperature control, as an example.
F# has many theoretical qualities, which make it fun if you like these things, but it also has some fundamental flaws, which is why it's not getting a wide professional adoption.
- the build system was a mess last I checked (slow, peculiar)
- syntax is not c-like or python-like (a big deal for a lot of people)
- you can't hire developers who know it (and certainly the few are not cheap)
- the community is a bit weird/obsessed/evangelizing (a turn off in a professional environment)
- it's clearly a second class citizen in the .net world (when stuff breaks, good luck getting support)
On the other hand
- it has discriminated unions
- units
- etc.
but do you need this stuff (not want: need)? most people don't.
A better graph would be of the number of people who self-report as being employed as software developer. I doubt that would show the same decline--there have not been many stories of people abandoning the profession because they could not find employment...
1. VSCode uses SSH (with its security profile) and the user can't do anything more with VSCode that they can already do with SSH. If the comparison is between a system without SSH and a system with VSCode and SSH--sure--I understand the concern, but it's an issue with enabling SSH and not VSCode.
2. VSCode can change files and persist? Well, it's a local editor, so yeah, it can change files and persist, that's literally its purpose. If that's an issue, disable editing permissions for the user.
Of course, I can be totally wrong but I've seen these things happen (I've been both a mod and a core dev at Stack closely working with the community team 8 years ago)
In reality most candidate are just bad at estimating their own skills (in both directions) and of course they know almost nothing about the match between the skills and the position.
- the candidate has a range of salary they expect or need
- the company has a range of salaries that they can pay
If these don't overlap there's no point going forward unless the range of the company is higher.
If these do overlap, it's worthwhile proceeding. Then it's a matter of skill. If you apply and ask for the top range in my salary band, and you are truly exceptional, I'll do my best to match it. But the ask needs to be commensurate to the skills you demonstrate in the interviews. The higher the ask, the stricter the criteria to match.
If you get to the end of the process without disclosing the salary, and you pass all interviews, I'll offer you for what I think you are worth. If you have an ask and did not disclose it, you might have just wasted everybody's time.
Believe it or not, negotiating a salary higher than your worth is a terrible idea. It might sound good, but it sets you up for failure.
It achieves only making queries much harder and much more opaque. It completely fails at that.
But then, you know, I don't involve 100k people in my projects...
There's the not-so-common case of needing database independence as well, but at that point DB perf becomes a really hard problem to solve generally...
Vocalizing primes? Maybe it could be used in speech synthesis although I'm not sure that the terms allow it or that the participants would be happy with their voice becoming AI...
- Conferences are usually not paid, except expenses. In fact the "compensation" for a speaker is to be able to travel and attend in person. Maybe for some this is a drawback, for me it's not.
- In person conferences allow you to meet and network with other speakers. Online conferences do not (unless you count "come to our discord" as networking, I don't)
- The value I get from conferences is also interacting with the public and listening to them, outside of the talks.
- I also don't really get any of the promotion value for my company, which obviously I represent.
In short, I understand they are cheaper to organize but the value is simply not there at all, so I will not speak at them, attend them, or sponsor them.
You can't do this stuff unless you have a working definition of personhood. Good luck with that. The moment that animals have rights you run into a huge series of ethical problems. Should dogs have rights? Should rats? Should insects? Should tardigrades? Should plants? Bacteria?
Most of these philosophical questions have no univocal answers and are usually the layperson can't go beyond "this cute animal has rights because I like it and this other animal doesn't because it's ugly", which frankly is appalling.
The big advantage is that the SQL engine can optimize the how if you focus on the what -- especially after so much research has been don building query compilers.
If you want to focus on the "how" then perhaps a "bare bones" DB like Redis is more in line with this kind of thinking.
Some developers have problems, because they don't understand its abstraction. Periodically they try to re-implement feature to "fix" SQL. Every time it's an absolute disaster.
I realize this is how the world works, but it's just a waste of time.
I've always said that Scrum doesn't fix problems, but it makes them more evident so you can fix them.
Teams that don't realize this are going to be unhappy about Scrum, but in my opinion they wouldn't be happy without.
Often the problems are one of these:
- Focusing on estimates. In scrum, a team doesn't really need any estimates beyond planning what they will do in the next two weeks. Planning poker, story points, estimations are just a means to that end. If you don't like them, don't use them.
- Focusing on ceremonies without understanding how to use them (or when to drop them!). I haven't done stand ups in years. I use online tools like geek bot. Retrospectives are just as useful as the number of problems you actually solve after they are pointed out. Planning is only useful if it produces teamwork, if the engineers all work in 1-person silos, it becomes a joke.
- Not understanding that Agile > Scrum. If you think you can be more agile without some parts of scrum, drop the parts you don't need. Being able to change the rules of the game in-flight is part of agile (and of scrum).
I write about coding, electronics, technical leadership and open source.
- https://sklivvz.com/posts/announcing-cthulhu-a-javascript-in...
- https://sklivvz.com/posts/i-dont-love-the-single-responsibil...
- https://sklivvz.com/posts/team-leadership-for-high-performan...
- https://sklivvz.com/posts/i-built-a-hardware-rng-for-christm...
More in general, it's absolutely wrong to think that modern music, especially rock, is adequately represented on a score or tablature, there's so much missing information on timing, volume, color...
Post Op is redefining surgical care, giving patients the ultimate recovery experience and providing clinical teams with more significant insights through AI-empowered communication. We aim to improve post-surgery care and reduce the global cost of surgical site infections.
Open positions: Mobile developer with AI skills, backend developer with AI skills
- the privacy commissioner is 78
- he doesn't have any tech background, he's a law academician
- the privacy commission office's home page still has a fax number on their front page, as of this morning
- the commissioner boasted in TV that he signed Musk's AI temp ban letter
- the official reason of the ban is that 12-year-old kids could potentially use the AI service, and OpenAI should instead filter them out
- no evidence that ChatGPT is bad for 12 years old is given
- no study on how many kids below 13 use the site, in relation to how many people overall in Italy
- he acted alone, instead as part of a commission, because he claims it was urgent
- no matter what, he is not liable for his actions by Italian law
Connect the dots anyway you like. I chose the following narrative:
At 78 he doesn't give a :poop:, he doesn't like progress because he's a boomer and abused his office to make a political statement because no one can touch him.
This is an absurd thought. AI content is still created by humans using AI, just like photos are created by humans using cameras.
Also who says that AI can't be as creative as humans or better? Why would humans be better at being creative "manually" instead of with machines?
I say AI creativity will be better than simple humans at creating stuff. Humanity will overall benefit from it and the world will be less dull.