257 private links
Deleting lines of code for optimisation and better maintainability.
I’m a web developer with ADHD, and I help people build the web better.
Builder of Kelp UI.
Instead of asking: I’m hungry, let’s go to McDonald’s
Why not: I’m hungry, let’s go eat: McDonald’s?
A “no, because” statement instead of a plain “no” moves the problem from a blocker into an opportunity.
Do not accept “we’ll figure that out later” as a response to pointing out meaningful problems. It’s a con.
Solve the problems or abandon the project.
Import et Export of software forges (issues, PR/MR, milestones, release assets, etc...)
A programming task implemented in multiple languages
"Vocational awe" describes the feeling that your work matters so much that you should accept all manner of tradeoffs and calamities to get the job done. ttarh uses the term to describe the pathology of librarians, teachers, nurses and other underpaid, easily exploited workers in "caring professions."
It describes example of how tech industry in the U.S. is starting to exploit tech workers too.
it’s amusing to consider how complicated modern software systems are that the developers themselves don’t know everything about them
True on the other side
A better method to hire devs.
That's why https://www.fightforthehuman.com/about/ started
All that's required is to create a malicious software package under a hallucinated package name and then upload the bad package to a package registry or index like PyPI or npm for distribution. Thereafter, when an AI code assistant re-hallucinates the co-opted name, the process of installing dependencies and executing the code will run the malware.
Aboukhadijeh explained that _Iain "automated the creation of thousands of typo-squatted packages (many targeting crypto libraries) and even used ChatGPT to generate realistic-sounding variants of real package names at scale. He shared video tutorials walking others through the process, from publishing the packages to executing payloads on infected machines via a GUI. It’s a clear example of how attackers are weaponizing AI to accelerate software supply chain attacks."
Defining seniority is a very tough thing. Though in my opinion a lot of being a “senior” is in soft-skills, when it comes to the technical hard-skills, a lot comes down to Fingerspitzengefühl. The longer you work with a language, framework or codebase, the more you develop this kind of intuition of what the correct approach is. The gut feeling of “something feels off” slowly turns into a feeling of “this is what we should do”.
About the many possible scenarios. Assumption on human names are false in the large majority of cases.
Bad #UI
experience: I was trying to send a friend some money via #CashApp
, but could not verify my identity. Here’s what their tech support found out:“...from the documentation you have provided, we see that you have a legal one letter name. While we understand that is the name chosen and legally granted, we regret to inform you that we cannot proceed with the request at this time.”
I sent a response thanking them for figuring out the problem, and I wouldn’t try to get verified -- or use CashApp -- again.
I also sent them the URL for “Falsehoods Programmers Believe about Names”
Names are changing and diverse. They are so different that a validator for them seems irrelevant.