HN user

aurelianito

2,003 karma

http://aurelianito.blogspot.com

mail me at aurelianocalvo at gmail dot com.

Posts75
Comments366
View on HN
www.zdnet.com 5y ago

The implications of low-code and no-code for developers

aurelianito
2pts1
news.ycombinator.com 7y ago

Ask HN: Suggestions to Make Alphago Zero Clone

aurelianito
2pts1
arstechnica.com 8y ago

A Cruise self-driving car got a traffic ticket–GM says it did nothing wrong

aurelianito
3pts0
www.foxnews.com 8y ago

Self-driving Uber crash could open the company to criminal charges

aurelianito
1pts0
www.wired.com 8y ago

Chrome extension malware has evolved

aurelianito
4pts0
mybroadband.co.za 8y ago

When programmers start coding

aurelianito
1pts0
arstechnica.com 8y ago

Self-driving Chevy Bolts are coming to the streets of Manhattan in 2018

aurelianito
2pts0
arstechnica.com 8y ago

Waymo's big self-drive car report

aurelianito
102pts43
www.businessinsider.com 8y ago

While Amazon and MicrosThis startup quietly built a $175M business

aurelianito
2pts0
news.ycombinator.com 9y ago

Ask HN: Where is “who is hiring”?

aurelianito
2pts3
evonomics.com 9y ago

Why Capitalism Creates Pointless Jobs

aurelianito
3pts1
www.carscoops.com 9y ago

Elon Musk Confirms Tesla Will Build European Gigafactory

aurelianito
1pts0
hothardware.com 10y ago

Google's DeepMind Is Developing an AI Kill Switch to Prevent a Skynet Apocalypse

aurelianito
1pts0
www.washingtonpost.com 11y ago

If a monkey takes a selfie in the forest, who owns the copyright?

aurelianito
3pts0
status.bitbucket.org 11y ago

Major outage in bitbucket (mercurial)

aurelianito
1pts0
dilbert.com 12y ago

Growth hacker

aurelianito
4pts0
blogs.wsj.com 12y ago

64,019 Searches: A Dark Journey Into My Google History

aurelianito
1pts0
arstechnica.com 12y ago

Increased human life expectancy correlates to increase in species extinction

aurelianito
1pts0
threatpost.com 13y ago

Microsoft launches $100,000 bug bounty program

aurelianito
2pts0
investor.staples.com 13y ago

Staples First Major U.S. Retailer to Announce Availability of 3D Printers

aurelianito
1pts0
bitslog.wordpress.com 13y ago

Satoshi ‘s Fortune: a more accurate figure

aurelianito
1pts0
bitslog.wordpress.com 13y ago

The Well Deserved Fortune of Satoshi Nakamoto, Bitcoin creator

aurelianito
273pts180
stackoverflow.com 13y ago

Stack overflow on stack overflow

aurelianito
1pts0
blogs.computerworlduk.com 13y ago

Python Trademark Filer Ignorant Of Python?

aurelianito
64pts24
permalink.gmane.org 13y ago

Emacs has evil inside

aurelianito
2pts0
www.facebook.com 13y ago

What is a hackamonth?

aurelianito
1pts0
news.ycombinator.com 13y ago

AWS EU region down?

aurelianito
1pts1
plus.google.com 13y ago

Alan Cox leaves Linux and Intel

aurelianito
251pts33
news.ycombinator.com 13y ago

EC2 console is not working properly

aurelianito
3pts1
muller.lbl.gov 13y ago

Astrology is not effective. A double-blind test from 1985.

aurelianito
1pts0

Semver is based on a lie. It assumes that you can define what is the proper behavior of a library. That's not necessarily true, and can be subtlety false, and different depending on the use case. I can think on some situations where I trusted semantic versioning and it bited me when an update was made. I am not talking about new bug introductions. I assumed behavoir that the library owner assumed as not important.

There should be no shame in younger people above ourselves. I am 46 and a coupple of years ago the CEO and CTO of the company I worked for were in their twenties. It did not bother me at all. If they do their jobs properly, it is fine at any age. If they dont do their jobs properly, it is not fine at any age.

I think that there are 2 foundationañ problems that make complex projects over budget: 1. Stakeholders are incentivized to negotiate down the budget, skewing the result. 2. Breaking down a big task into smaller ones comes with the risk of missing some activities, but adding a nob-required subtask is almost imposible, also skewing the results.

Estimates of big endevours must be made by comparison instead of breaking down the tasks to avoid the second issue. That's one of the little secrets that make poker planning succesfull.

Extra points: leave old and outdated documentation and scripts in the repository. New documentation should go to a wiki that is not referenced in code and does not track versions. Different parts of the wiki should apply to different code versions.

That's not true. It needs to recharge a part of the electricity used. For example, if it provides 2/3 of the electricity being used it would potentially triple the range.

Commit early. But do not commit garbage. Each commit should be a small but meaningful advance. All tests should pass. If working with compiled code, off course it should compile. No todos. No clunky var or method names. A branch per merge request.

If you do it like this it is great for everyone. Do not squash commits or rebase. Those are antipatterns. We are lying to ourselves when we do it. We cannot learn from history we rewrite.

The difference is that nVidia would not be able to remove your NFT from its db of serial numbers, because the association between the number and you, instead of being in a DB it is in the blockchain itself, and the only one that can change that association is the holder of the NFT.

Both CommonJS and ES6 modules suck. The way things should have been is requirejs. Modules are defined and loading using an API instead of having reserved words. It's really sad what happened to modules in JavaScript.