Overtime work can cause liver damage, and overtime work in our company can cause head damage!
A weird high-paying offer allowed me to join this company called "Eternal Technology".
On my first day at work, I got a copy of the "Employee Code of Conduct" that was thicker than a brick.
[It is forbidden to wear red, otherwise you will become the target of "it".
[Please get down when you hear the sound of marbles after ten o'clock, because the "patrol" begins.
[The most important thing: Please work hard to survive. The company does not support idle people, let alone dead people!
I, Lin Mo, am an ordinary programmer.
When my colleagues evaporate out of thin air in front of me, when twisted monsters wander in the corridors late at night...
I discovered that this company is not a person!
The only thing I can rely on is the logic of my code.
They have rules, and I can find bugs!
Reader comments
A small suggestion: modules that provide services to the upper layer should hide their implementation details. This is also the idea of encapsulation in programming. I think the same goes for writing a book. Reduce the code-related content in the book, replace professional terminology, appropriately delete modifications that are useless to promote the plot, and excessive descriptions. Simplify the content that should be simplified, and render the parts you want to highlight. You should write a book so that as many people as possible can understand it, and focus on expressing the meaning clearly. Please stop spending so much time and ink on things like time and space complexity, traversal, etc. You can't say that the difficulty of the plot is only driven by the complexity of the algorithm. What everyone wants to see is not incomprehensible things like Kruskal and Dijkstra's algorithm. As for readers who have learned programming, I guess what they want to see more is a beautiful girl with white hair and red pupils who is 1.5 Meters tall and has cat ears [eating melon]
I like it, suitable for watching at work.
First, where did the bracelet and door come from at the old man's house, something that can deliver food suddenly appeared. Second, if the auditor is a system administrator, there is no program that can resist it. It is more appropriate to set it to an anti-virus program.
A very interesting book, a must-read for old bookworms
NB, I can still learn some, but it's just some basics.
Good reviews, the subject matter is novel and logical, I hope more people will read it
A small suggestion: modules that provide services to the upper layer should hide their implementation details. This is also the idea of encapsulation in programming. I think the same goes for writing a book. Reduce the code-related content in the book, replace professional terminology, appropriately delete modifications that are useless to promote the plot, and excessive descriptions. Simplify the content that should be simplified, and render the parts you want to highlight. You should write a book so that as many people as possible can understand it, and focus on expressing the meaning clearly. Please stop spending so much time and ink on things like time and space complexity, traversal, etc. You can't say that the difficulty of the plot is only driven by the complexity of the algorithm. What everyone wants to see is not incomprehensible things like Kruskal and Dijkstra's algorithm. As for readers who have learned programming, I guess what they want to see more is a beautiful girl with white hair and red pupils who is 1.5 Meters tall and has cat ears [eating melon]
I like it, suitable for watching at work.
First, where did the bracelet and door come from at the old man's house, something that can deliver food suddenly appeared. Second, if the auditor is a system administrator, there is no program that can resist it. It is more appropriate to set it to an anti-virus program.
A very interesting book, a must-read for old bookworms
NB, I can still learn some, but it's just some basics.
Good reviews, the subject matter is novel and logical, I hope more people will read it