There are some tasks, especially the ones that involve deleting folders as SU, that I do thoughtfully and slowly before I press the Enter key. I think if others saw me do these at the careful pace that I do they would cringe. Are there critical programming tasks that you perform that you believe deserve this thoughtful and careful consideration?
有一些任务,特别是那些涉及删除文件夹作为SU的任务,在我按下Enter键之前我做得很周到。我想如果其他人看到我以我认真的速度做这些,他们会畏缩。您认为值得仔细考虑的是否需要执行重要的编程任务?
13 个解决方案
#1
14
Changes to live databases, actually I do a backup first just in case even know I'm extra careful :)
对实时数据库的更改,实际上我先备份,以防万一甚至知道我特别小心:)
#2
12
It's kind of a programming task, because if I do it wrong, it will affect my ability to get paid for programming: Write emails on touchy subjects or to touchy people.
这是一种编程任务,因为如果我做错了,它将影响我获得编程付费的能力:在敏感的主题或敏感的人上写电子邮件。
It can take me an hour to get the tone of a one paragraph email just right.
我可能需要一个小时才能获得一段电子邮件的语气。
#3
5
Anything that irrecoverably changes important data. I've learned my lesson the hard way, several times.
任何无法恢复重要数据的东西。我已经多次学到了很多教训。
#4
4
A release process is usually a methodical thing for me.
对我来说,发布过程通常是一种有条理的事情。
#5
4
Everything. I've never been a "just dive into it" programmer. Always have, always will be.
一切。我从来就不是一个“只是潜入它”的程序员。永远拥有,永远都会。
#6
1
Submits - 'cause its embarrassing if I break a test.
提交 - 如果我打破测试会导致尴尬。
#7
1
Code to evaluate the accuracy of something I'm developing. Otherwise, I spend all this time making the other code production-ready, only to find it doesn't compute the right thing after all.
代码来评估我正在开发的东西的准确性。否则,我花了所有这些时间让其他代码生产就绪,只是发现它毕竟不能计算正确的东西。
#8
0
Common code. I.e. changes to old, shared code which is used in multiple independent programs.
常用代码。即更改为在多个独立程序中使用的旧共享代码。
#9
0
Kernel driver stuff - cause those blue screens are a pain !
内核驱动程序的东西 - 导致那些蓝屏是痛苦的!
#10
0
Any collection juggling, especially in C (all it takes is one off by one error to shotgun your heap).
任何集合杂耍,特别是在C中(所有需要的是一次性错误来霰弹你的堆)。
#11
0
On the DB side, if I run an update/insert/delete and I don't want to backup the whole database, I always select * into myTable_backup from myTable
在数据库方面,如果我运行更新/插入/删除并且我不想备份整个数据库,我总是从myTable选择* into myTable_backup
#12
0
if make big changes in Visual Studio eg a big refactoring or maybe re-organising solution\project structure I will do it on a copy of solution first to see if there are any gotcha and that the bloody thing will still compile and play nice. Once satisfied this is the case I will do it on code under source control.
如果在Visual Studio中进行大的改动,例如大的重构或者可能重新组织解决方案\项目结构,我将首先在解决方案的副本上进行,看看是否有任何陷阱,并且血腥的东西仍然可以编译并且玩得很好。一旦满意,我将在源代码管理下的代码上执行此操作。
I do this because I have experienced situations where the 'rollback' functionality of whatever source control you are using won't let you rollback as required and\or does not get it %100.
我这样做是因为我遇到过这样的情况:你使用的任何源代码控制的“回滚”功能都不会让你按需要回滚,或者不会得到%100。
#13
0
Doing get from SourceSafe — really easy to hit a wrong button and lose your local version that you've been working on. /I hate SS, but am forced to use it./
从SourceSafe获取 - 很容易找到错误的按钮并丢失您正在处理的本地版本。 /我讨厌SS,但我*使用它./
#1
14
Changes to live databases, actually I do a backup first just in case even know I'm extra careful :)
对实时数据库的更改,实际上我先备份,以防万一甚至知道我特别小心:)
#2
12
It's kind of a programming task, because if I do it wrong, it will affect my ability to get paid for programming: Write emails on touchy subjects or to touchy people.
这是一种编程任务,因为如果我做错了,它将影响我获得编程付费的能力:在敏感的主题或敏感的人上写电子邮件。
It can take me an hour to get the tone of a one paragraph email just right.
我可能需要一个小时才能获得一段电子邮件的语气。
#3
5
Anything that irrecoverably changes important data. I've learned my lesson the hard way, several times.
任何无法恢复重要数据的东西。我已经多次学到了很多教训。
#4
4
A release process is usually a methodical thing for me.
对我来说,发布过程通常是一种有条理的事情。
#5
4
Everything. I've never been a "just dive into it" programmer. Always have, always will be.
一切。我从来就不是一个“只是潜入它”的程序员。永远拥有,永远都会。
#6
1
Submits - 'cause its embarrassing if I break a test.
提交 - 如果我打破测试会导致尴尬。
#7
1
Code to evaluate the accuracy of something I'm developing. Otherwise, I spend all this time making the other code production-ready, only to find it doesn't compute the right thing after all.
代码来评估我正在开发的东西的准确性。否则,我花了所有这些时间让其他代码生产就绪,只是发现它毕竟不能计算正确的东西。
#8
0
Common code. I.e. changes to old, shared code which is used in multiple independent programs.
常用代码。即更改为在多个独立程序中使用的旧共享代码。
#9
0
Kernel driver stuff - cause those blue screens are a pain !
内核驱动程序的东西 - 导致那些蓝屏是痛苦的!
#10
0
Any collection juggling, especially in C (all it takes is one off by one error to shotgun your heap).
任何集合杂耍,特别是在C中(所有需要的是一次性错误来霰弹你的堆)。
#11
0
On the DB side, if I run an update/insert/delete and I don't want to backup the whole database, I always select * into myTable_backup from myTable
在数据库方面,如果我运行更新/插入/删除并且我不想备份整个数据库,我总是从myTable选择* into myTable_backup
#12
0
if make big changes in Visual Studio eg a big refactoring or maybe re-organising solution\project structure I will do it on a copy of solution first to see if there are any gotcha and that the bloody thing will still compile and play nice. Once satisfied this is the case I will do it on code under source control.
如果在Visual Studio中进行大的改动,例如大的重构或者可能重新组织解决方案\项目结构,我将首先在解决方案的副本上进行,看看是否有任何陷阱,并且血腥的东西仍然可以编译并且玩得很好。一旦满意,我将在源代码管理下的代码上执行此操作。
I do this because I have experienced situations where the 'rollback' functionality of whatever source control you are using won't let you rollback as required and\or does not get it %100.
我这样做是因为我遇到过这样的情况:你使用的任何源代码控制的“回滚”功能都不会让你按需要回滚,或者不会得到%100。
#13
0
Doing get from SourceSafe — really easy to hit a wrong button and lose your local version that you've been working on. /I hate SS, but am forced to use it./
从SourceSafe获取 - 很容易找到错误的按钮并丢失您正在处理的本地版本。 /我讨厌SS,但我*使用它./