The success and failure of Ninja (2020) • Hacker News Board

Re: The success and failure of Ninja (2020)

#81

Post by nuclearnice3 » Sat, Nov 30, 2024, 11:12 PM UTC

zemvpferreira wrote: post #48

pydry wrote: post #38

Earlier quoted context omitted.

>Executives want everyone to be widgets except themselves Of course. This maximizes their relative power within the company. Some executives are focused on the health of a company as a whole but not many. To most of them the pie can be assumed to be a fixed size and their job is to take as much of it as possible.

For businesses or business areas where excellent isn’t necessary and good will do, this attitude can even be considered to be in the best interest of the company. The more fungible employees are made, the less bargaining power they have.

Fair point. You could also imagine it's an easier management task to have fungible employees. Sam quits. No risk to the company. Our employees are fungible. Sarah can step right in.

Re: The success and failure of Ninja (2020)

#82

Post by morning-coffee » Sun, Dec 01, 2024, 3:16 PM UTC

Krastan wrote: post #23

grobibi wrote: post #9

I thought this was going to be about people buying less air fryers.

I thought this was going to be about the Fortnite streamer

I thought it was going to be about the lead singer of Die Antwoord.

Re: The success and failure of Ninja (2020)

#83

Post by Agingcoder » Sun, Dec 01, 2024, 7:28 PM UTC

Swizec wrote: post #5

willvarfar wrote: post #4

> we talk about programming like it is about writing code, but the code ends up being less important than the architecture, and the architecture ends up being less important than social issues. A thousand times this! This puts into words something that's been lurking in the back of my mind for a very long time.

In my experience roughly 80% of technical issues are because 2 people (or teams) didn’t want to just sit down together and talk it out.

Yes, because ‘they’ ( the other team ) are not doing it right so not talking is best

Re: The success and failure of Ninja (2020)

#84

Post by Agingcoder » Sun, Dec 01, 2024, 7:32 PM UTC

dahart wrote: post #74

marcosdumay wrote: post #72

Earlier quoted context omitted.

For a start, more speed would be great. It's slow to start, end, and slows down the code so much that it has semantic implications. Also, it can fail loudly if it loses the control of the target process or if the target process fails before it finishes connecting. Also, it should not run after the UI reports that it finished.

So I’m still left curious which debuggers are much better than VS? What do you mean about so slow there are semantic implications? How does execution speed change meaning? Can you give an example? And are you talking about VS specifically, or just debugging in general? Gdb can be extremely slow when debugging too, and besides that, simply turning on symbols and turning off optimizations can be a major reason for slow…

Pernosco https://pernos.co/ Is vastly better than any debugger I’ve ever used.

Gdb is horrible, vs debugger is quite good but has strange limitations

Re: The success and failure of Ninja (2020)

#85

Post by zemvpferreira » Mon, Dec 02, 2024, 4:38 PM UTC

nuclearnice3 wrote: post #81

zemvpferreira wrote: post #48

Earlier quoted context omitted.

For businesses or business areas where excellent isn’t necessary and good will do, this attitude can even be considered to be in the best interest of the company. The more fungible employees are made, the less bargaining power they have.

Fair point. You could also imagine it's an easier management task to have fungible employees. Sam quits. No risk to the company. Our employees are fungible. Sarah can step right in.

I guess so. As a business owner/administrator it’s easy to see how your interests align in this way. As a worker your priority should be the opposite of course.