Safari on Windows and a kind of harmful thinking from student time

One day I was at work late, until I came back to find another team working hard. I ran back to greet you guys, the screen is . Safari version of Windows. My friend is testing (testing) a new system on Safari for Windows.

Perhaps, everyone who read here is as amazed as I was then. Apple has stopped developing Safari for Windows since 2013, that is, five years ago. Try looking around you: Windows users, if not Chrome, use Coc Coc, Firefox or Edge. Some corporations still use Internet Explorer, but the worst is from version 8, the majority have switched to Internet Explorer 11. There is absolutely no reason to support Safari on Windows.

Safari on Windows: A software is dead and should not exist in any project anymore.

As a student, during the 'Cloud Computing' class, the teacher let us choose any topic to practice. I chose a very 'buzzing' theme as 'Deploying apps to Google App Engine'. It sounds very loud, but actually I just wrote a 'application' with 2 names and date of birth, and instead of installing the application on my computer, I 'implemented' on Google.

He gave me the answer, I got 8. But in the next lesson, he gave me a rather difficult topic for me: integrating my application with the Amazon cloud. The reason is because in the 'future development direction' section of the first article, I write 'further integration with the Amazon database'.

Why do I write that? Because an online blog about Google App Engine writes the same thing. And I . "learn" from that lesson.

Everyone who goes to school knows the "butt cheek" mentality so that what they write seems more professional and fuller.

How are my two stories the same? In essence, the way of writing software documentation is similar to the way we often do student essays. Almost no one writes a completely new document from scratch, instead it will be based on an existing document, of the IEEE, of the old project, of . someone online. When creating new material, writers will often focus more on the feature description - which is where their creativity and thinking are concentrated. Other parts, from the document's description of performance to performance / stability requirements, are often copied.

Sadly, the 'supported browser' section of the project documentation belongs to the copied group. When I asked you to write a project document, you said innocently: 'I copied from the old document enough.'

Because of the documentation, your team still tests on Safari - the company needs to show the highest level of seriousness to the customer. But it could also be because our customers don't . read back the material we provided. If so, I'm sure they furrowed their eyebrows when they saw Safari on Windows.

Going to school is to get points for yourself, sometimes 0 points okay.

This is the way 'thinking it has' from the time students are affecting us. That day, as students, the things we made outright were largely of little practical value, knowledge taken from others. In many ways, we are trying to make what we do look more professional, more beautiful to hide our true amount of gray matter. "Future development" is one such way. A good article for a difficult topic will not need to add this section and still be easy to get 9 or 10.

When working, we also forget that the perspective of the boss, the customer is also different from the teachers. Some teachers allowed to copy 'as long as they had to understand and explain', some teachers banned it very tightly. But teachers all post and grade according to the composition. You can make 4 sentences out of 5, you can still get 8.

Going to work is not so. Everything that is part of our responsibility can have consequences. Writing the 'supportive browser' in a sufficiently copied manner has resulted in a huge amount of work for the team.

Working is taking responsibility, with yourself, with your team, with your boss.

Do not let yourself fall into such circumstances. It is better to not copy that part, we still have the opportunity to negotiate with customers - certainly if they negotiate, they will also put 'Safari on Windows' for my company. Instead of looking at a very pointless copy, they may have directed their entire attention and compliments to the cool features we designed for them.

Do not let yourself fall into such circumstances. Get rid of the 'butt cheek' thinking now, 'add it all' from today.