On Tue, Dec 31, 2019 at 11:56:46PM -0700, Bob Beck wrote:
>read fucking code. change fucking things. send some fucking diffs. get
>fucking yelled at. learn from your fucking mistakes. show some fucking
>passion. filter fucking misc@ and all this useless bleating into the
>toilet.
>
>none of us have time to spoon feed you in some "boot camp"
>
>there are two types of programmers. the self taught, and the hopeless. it
>is your job to turn yourself from the hopeless to the self taught.
>
>shut up and fucking hack.
Well put.
But I don't want deeper point to get missed -- which is that if eecd
doesn't like the idea of regulating what the programmer can do, then the
programmer has to have the skills to safely write unsafe code.
>
>
>On Tue, Dec 31, 2019 at 23:50 Frank Beuth <seclists@boxdan.com> wrote:
>
>> On Wed, Jan 01, 2020 at 04:00:37AM +0000, eecd@isdaq.com wrote:
>> >rather than the programmer being responsible for
>> >writing unsafe
>> >code we need to regulate what the programmer can do just like we need to
>> >regulate what the community can say, do, see, and think.
>>
>> where do I sign up for OpenBSD write-perfect-C-code programmer training
>> bootcamp?
>>
>>
No comments:
Post a Comment