ncouture

The title of the original article feels like click-baiut to me. It's covering an act of violence under the pretext that people hate AI.

In fact it's a very sad story about a 20 year old throwing their life away instead of fighting for what he believes is right through non-violent activism and/or regulations.

Last year I wrote an article asking the very question "Who will be the next Luddites?", National Geographics followed-up months later. I'm sure many before, after or in-between covered the same topic. There is truth to it, we will be impacted but let's not forget we went through this during the industial revolution and we should be better equipped than ever to fight using meaningful non-violent acts and operations.

https://www.linkedin.com/pulse/who-neo-luddites-more-importa...

http://nationalgeographic.com/history/article/luddite-indust...

https://en.wikipedia.org/wiki/Luddite

https://en.wikipedia.org/wiki/Neo-Luddism

I planned on not leaving it online but wanted to test how much traffic it could drive. Nothing. 500 views.

I would absolutely not consider this overreaching if the statement within this thread that "it had referred the user to mental help hotlines multiple times in the past" is true.

That reaches near the fact that a lot of AI is not ready for the enterprise especially when interconnected with other AI agents since it lacks identity and privileged access management.

Perhaps one could establish the laws of "being able to use AI for what it is", for instance, within the boundary of the general public's web interface, not limiting the instances where it successfully advertises itself as "being unable to provide medical advice" or "is prone to or can make mistake", and such, to validating that the person understands by asking them directly and perhaps somewhat obviously indirectly and judging if they're aware that this is a computer you're talking to.

It sounds more poetic than an invitation or an insult that invites someone directly or not to kill themselves, in its own, in my opinion.

This isn't Gemini's words, it's many people's words in different contexts.

It's a tragedy. Finding one to blame will be of no help at all.

I can delete it if you want.

You might have a point but I also stand by the point of view of the reply you reply to. It's personal opinion.

In this case, your intuition is right, I threw this around as fast I could to find out if little would go a long way.

It went further than I thought and I appreciate the various views this sparks. Though it's completely irrelevant to the topic at hand, it's rightly so.

Leviticus 11:3, "Whatsoever parteth the hoof, and is cloven footed, [and] cheweth the cud, among the beasts, that may ye eat."

One must learn to walk the walk not merely talk the talk. :-)

No but yes.

Ah, there it is. I'm starting to feel sorry and only got 30 upvotes.

If it's of interest to anyone, I have not used any alternative means of advertising this YC post other than posting it here and using 2 alt accounts to write the first two replies and two upvotes.

What `kisscalls` said as `remote` is true.

We are looking at high-level operant conditioning disguised as standard startup advice. The most fascinating tactical deployment happens at [22:56]—the 'Socratic Trap.' Notice how they advise inducing a micro-stressor (asking the founder why they will fail) to shatter the target's rehearsed 'pitch mask' and force cognitive overload. It’s a textbook elicitation technique to establish a baseline of the founder's true risk tolerance.

Which influence tactic or behavioral shift stood out to you the most in this briefing? Drop your profiling observations below—I’ll be analyzing the best ones.

This is an awesome features for quick development.

I'm sure the documentation of this featureset highlights what I'm about to say but if you're attracted to the simplicity of writing Python projects who are initialized using this method, do not use this code in staging/prod.

If you don't see why this is not production friendly it's for the simple a good.reaaon that creating deployable artifacts packaging a project or a dependency of a project this uses this method, creating reproducible builds becomes impossible.

This will also lead to builds that pass your CI but fail to run in their destination environment and vice versa due to the fact that they download heir dependencies on the fly.

There may be workarounds and I know nothing of this feature so investigate yourself if you must.

My two cents.

Had to look closer into it, there's a nice audio file of it here: https://en.wiktionary.org/wiki/shy_bairns_get_nowt

Thanks for the honest feeback. Also shortened my comment considerably to keep it to my thoughts and not the ones expressed in by the author of this article.

On the rare occasion I make an effort to contribute my thoughts in a positive way I get downvoted but nobdy even mentions why.

Is it that obvious? Maybe someone else can tell me? I'd like to understand if it can help me improve my online etiquette or the HN rules better.

Rejection is not a big deal, and you should just move on.

This is the reason I looked past the rejection argument in my reply below; because there is so much more to gain from sharing than to lose from rejections.

I don't understand why my first reply below is being downvoted. If someone disagrees and downvotes at least drop a note that would make sense. :-)

There's a range of reasons why sharing ideas help foster a positive culture of creativity so if you don't already have a time and place to do so I strongly suggest brainstorming, 10xing, or whichever other method makes this process easy on groups of individuals. It's a lot of fun and we get a lot out of it.

  - you never know who might be interested in your idea
  - putting your ideas out there helps you to get feedback and improve upon them
  - it's an opportunity to practice articulating your ideas to others
  - sharing your ideas can inspire others, help in creating a community of support around you and your work (culture++)
  - getting your ideas out there can help you to build momentum, gain traction, find allies in your project or business
  - sharing your ideas with others they could lead to new opportunities or connections that you never would have otherwise

You're very right about everything you said.

However at the end of the day, what's important to me is to feel I've tried doing the right thing.

This means I can't do things conditionally or "only if I trust my manger won't take credit for it". If I want to be credited for my work, I feel that it's mostly my responsibility take credit for it.

It can be very difficult to change people, teams, processes, companies so I understand why we may want to get something out of trying hard to improve things we feel others should want to improve as well. It's not always as obvious as "a salary increase" or "public recognition", but employees who try to improve processes indicates to management they are interested in sharing their input and committed to making things better. This fosters credibility, and creates a more positive work environment.

Job hopping may often be easier but is often seen as a red flag by employers and it can make it difficult to build a strong, long-term career.

What is unfortunate in my opinion is working with developers unwilling to learn more about systems and infrastructure. With the rise of DevOps, it's often the norm that many developers don't know how to do some part of their job. As opposed to your comment this is not on the level of "developer who doesn't know how to code" but "developer who don't know how to work with the underlying systems, builds, deployment processes, and the underlying infrastructure powering their code".

When people are unwilling to learn from others, they are missing out on opportunities to grow and improve. This can lead to a feeling of being stuck in a rut, and can ultimately lead to dissatisfaction with one's job or career; as much for people who lack some expertise and are unwilling to learn, than for those who can help them increase their competence in this closely related field of work, who often end up doing most of the work in this field

Here's a translation of the Russian propaganda:

    "From the testimony of the captured commander of the 36th Marine Brigade of the Armed Forces of Ukraine, Colonel Dmitry  Kormyankov, it turns out that the internet terminals of Elon Musk's Starlink satellite company were delivered to the militants of the Nazi Azov Battalion and the Ukrainian  Marines in Mariupol by military helicopters.

    According to our information, the delivery of the Starlink  Equipment was carried out by the Pentagon.

    Elon Musk, thus, is involved in supplying the fascist forces in Ukraine with military communication equipment. And for this, Elon, you will be held accountable like an adult - no matter how much you'll play the fool."

Source:

1. https://twitter.com/elonmusk/status/1523462998081572864

2. https://twitter.com/elonmusk/status/1523464037048020992

What matters the most is the results. In my opinion a decision like the following is totally reasonable providing you are looking for people that owns your results to be in charge:

  during a factory visit over issues with the Model X's 
  window. When a worker on the assembly line proposed a 
  solution, Musk lit into the worker's manager.

  "This is totally unacceptable that you had a person working
   in your factory that knows the solution and you don't even
   know that," Musk reportedly said before firing the head of
   the factory.

You can follow the story as a step-by-step tutorial, while running every serverN.py examples at the same time they say they run them and then use telnet and/or netcat like they say they use it in the story.

If you really want to understand this it'll be easy enough, connect to irc.libera.chat, join say ##linux or even better #networking and ask any question that comes to mind.

I'd advise anyone to do it; this little story is one of a kind.

Any; from my experience developing voice UIs using Google products and APIs I figured it was a very good thing to segregate the application logic from its integration with select platform(s) like Google Actions, Alexa skill, Android Things, a standalone device, or one of many 3rd party chat application like Facebook Messenger or Hangouts Chat...

There are so many options it seems like the right thing to do is to release on those your potential users have access to.

While I think this (like Slack) can provide value and might be welcome by some as a great tool for work I cannot stress enough the fact that from my experience chat for work becomes misused when it's allowed or encouraged to be used for organizational purposes.

At a glance it seems to me you might have found a good use for it, just please remember where chat starts and ends being a useful tool as it seems to me more and more people use it for things it is not good at.

Do educate me if you think I'm missing it's point.

I would like to see this kind of service work to allow meeting fellow local hackers.

If interested please contact me (nicolas@kisscalls.com); I would like to donate to you the domain name "hackers.express".

This sounds interesting. Is there a reason it is limited to Alexa users?

Yes.

Assuming Oracle has a very strong corporate environment as I expect it to, one could presume that many of their employees might be less inclined toward taking initiatives, ownership, and the likes while perhaps being better at taking directives.

All else equal, we cannot fit people into a mold; your interview process should help you answer these questions.

My two cents.

What you say is true; I learned, and am still reminded of it, the hard way from time to time.

But it's nothing more than a problem waiting to be solved.

In my case I'm solving this problem by using static sites and managed web hosting.

Put simplicity where simplicity is due and segregate the more complex requirements. Static sites are going a very long way now, and a lot can be done with JavaScript on the client-side with modern browsers.

In many cases no back-end services are needed, but when they are, it can make a lot of sense to segregate them in a way they can power multiple sites with the same functionality requirements.

It's really up to the needs you have but in the end I feel it can really be worth it.

Heck, latest web standards let us componentize elements, we might all be better off with a global database that contains all of them in JSON or YAML format which we can load/dump from and that contains some kind of ACL (ala Firebase can do that).

Have a good day.

Guess how many side effects have been widely known since the 1970's?

Does this make it fine not to expect a doctor to inspect the list of known side effects for drugs his patients are taking?

I've heard this very story a few times already, perhaps the sources of data widely accepted by doctors are not up to par with what non-doctors consider as accurate, in some cases anyway.

You're at least partly right about sites being crawled differently depending on popularity. I think the factors may not be limited to popularity alone, but we see this behavior documented in the crawling rate documentation Google provides its users/clients so there is no reason it couldn't apply to other "expensive" actions their crawlers do.

How this might work with the most popular sites out there?

We see it in on-page answers that provide extracts of pages with the answers to questions asked in search phrases that include a reference to the document they were sourced from.

Matt Cutts used to qualify sites like Wikipedia as "reputable" to the eyes of the search engine.

Thanks for sharing your notes, I'm sure they will help someone sometime.

It's interesting to see that another person who's excited to share his notes is also an Emacs and org-mode user.

For what it's worth, here are mine: https://ncouture.github.io/

If you're interested in the export process: I use the Nikola static site generator to publish some of my org file as it supports multiple markup formats including org.

https://getnikola.com/