HN user

asimuvPR

1,597 karma

asimuv is currently on suspended animation :)

Posts7
Comments636
View on HN

I feel this is meant as:

"If you want to present at a big conference, then you must have experience doing smaller conferences or presentations."

You can gain experience by presenting in local meetups, making videos and posting them online, doing short tech talks at your job, etc. Doing those first will net you a lot of valuable skills and experiences.

Some people are able to do it. But most are exaggerating or not doing the exercises. It takes me weeks to properly finish a good technical book due to time constraints. Either way, just do your best and forget about anybody else.

I've worked on enough projects to have covered both sides of the equation. The pristine codebase that belonged on a museum yet took way too much time to ship a feature. The other side of the coin with the codebase that somehow worked (no one knew how) and brought in millions because people would keep piling stuff on top of it. Have also worked with a codebase that started off awfully and was cleaned up enough to reduce the amount of time lost on stupid bugs and and thus increased how effective the team was delivering new features (with a direct financial improvement as a result because sales picked up significantly). It all boils down to finding a balance. Sadly, people confuse technical perfection with a product that works.

I've been in the game long enough to realize how true this is. Good point. It will certainly make people here defend their sacred choices.

I do STEM Q&A sessions at schools various times a year. I cannot mentor anyone at the moment, but I could schedule time and do a Q&A session with them. No strings attached. Email in profile.

Disclaimer: I work in Ed-Tech. This is in no way a sales pitch.

There is a real risk related to goal oriented AI. It does not need to feel or dream. Merely having survival as its goal is sufficient to make it dangerous to other life forms. Worse is that it can happen at any time (it may have happened already). Given the computing power, tools, and availability of knowledge we can assume that it can be done outside of a controlled lab environment by a non-scientist.

This sentence[1] from his website always makes me chuckle:

Although my professional truck-driving career was brief, I did learn enough to do a nearly perfect double-clutch with a non-synchromesh transmission, while driving up a hill on a forest track, carrying a bunch of kids in the back of a dumptruck--the tippable, flat-bed kind, not one designed to squash garbage.

He left us too early.

[1]https://www.bell-labs.com/usr/dmr/www/otherlives.html

Windows 93 (2014) 10 years ago

The snake game music when you click to defrag... Felt young and old at the same time.

Sometimes we just want to do something new for a short time. It might be to try some new library or language. Thats ok. Learn to identify what is a short term project (I want to learn how to do n with python) and a long term project ( I want to learn Ruby). In the case if building products, use the MVP approach. Then build on it if required.

I suffer from this, too. My solution has been to just write whatever code comes up and then commit it to its own branch. The anxiety of doing things right is then removed by the action of doing it. I can later revise the code and fix whatever issue it may have. Try it out. Its liberating.