Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Guides
Programming Guides & Questions
[Theory] Native Windows API (NTAPI)
Message
<blockquote data-quote="tim one" data-source="post: 738007" data-attributes="member: 25920"><p>Silly comments against me but your post doesn't change things for me and don't tell me that during your courses/job you’ve implemented everything, tried everything and came accross every problem you could find, because this is just a BULLSHIT!</p><p></p><p>For example.</p><p></p><p>Do you understand why a hash table needs to be rehashed ?</p><p>Yes? So you have implemented one and tried to optimize it...right!?</p><p></p><p>Do you really understand SQL indexes (and use them properly)?</p><p>Yes? So you know what data cardinality is and how it affects binary trees... right!?</p><p></p><p>Do you really understand OS scheduling?</p><p>Yes? So you have tried to implement a minimal kernel yourself and saw the problematics behind it....right!?</p><p></p><p>Do you really understand the difference between reserved and committed memory? Yes? So you have implemented even the simplest memory allocator just for the ##### of it....right!?</p><p></p><p>I firmly think and ALWAYS say that there are two kinds of knowledge:</p><p></p><p>1) the one you have because someone explained to you something and you understood that or not;</p><p>2) the one you get because you bang yourself against the same problems and you find out the best solution for the problem.</p><p></p><p><strong>I go for the second one so I hope you understand that I don't need lessons from you or anyone else!</strong></p><p></p><p>I'm done here.</p></blockquote><p></p>
[QUOTE="tim one, post: 738007, member: 25920"] Silly comments against me but your post doesn't change things for me and don't tell me that during your courses/job you’ve implemented everything, tried everything and came accross every problem you could find, because this is just a BULLSHIT! For example. Do you understand why a hash table needs to be rehashed ? Yes? So you have implemented one and tried to optimize it...right!? Do you really understand SQL indexes (and use them properly)? Yes? So you know what data cardinality is and how it affects binary trees... right!? Do you really understand OS scheduling? Yes? So you have tried to implement a minimal kernel yourself and saw the problematics behind it....right!? Do you really understand the difference between reserved and committed memory? Yes? So you have implemented even the simplest memory allocator just for the ##### of it....right!? I firmly think and ALWAYS say that there are two kinds of knowledge: 1) the one you have because someone explained to you something and you understood that or not; 2) the one you get because you bang yourself against the same problems and you find out the best solution for the problem. [B]I go for the second one so I hope you understand that I don't need lessons from you or anyone else![/B] I'm done here. [/QUOTE]
Insert quotes…
Verification
Post reply
Top