KASR1 - Professional Profile

Action

Author

Authority

Debator

Editor

Enquirer

Organiser

Participant

If Owner

Member Types

Have no restrictions on voting frequency

silver

Bypass spam checks when posting content

silver

gold

SubEditor, Mentor, Protector, Editor

Store personal files in your account area

platinum

SubEditor, Editor

Have live hyperlinks in your profile

bronze

silver

SubEditor, Protector, Editor

Have the ability to include a biography in your profile

bronze

silver

SubEditor, Protector, Editor

Edit a Question in Q&A

silver

Yes

SubEditor, Protector, Editor

Edit an Answer in Q&A

silver

Yes

SubEditor, Protector, Editor

Delete a Question in Q&A

Yes

SubEditor, Protector, Editor

Delete an Answer in Q&A

Yes

SubEditor, Protector, Editor

Report an Article

silver

SubEditor, Mentor, Protector, Editor

Approve/Disapprove a pending Article

gold

SubEditor, Mentor, Protector, Editor

Edit other members' articles

SubEditor, Protector, Editor

Create an article without requiring moderation

platinum

SubEditor, Mentor, Protector, Editor

Approve/Disapprove a pending Question

Protector

Approve/Disapprove a pending Answer

Protector

Report a forum message

silver

bronze

Protector, Editor

Approve/Disapprove a pending Forum Message

Protector

Have the ability to send direct emails to members in the forums

Protector

Create a new tag

silver

Modify a tag

silver

Sakthi_Vel wrote:
Please tell me how to start

excerpt from this link[^]

As far as I can tell, it’s because many so-called programmers just don’t know how to build a compiler. I really don’t have much patience for this sort of thing. To my mind, there is a minimum set of topics with which you have to be conversant to call yourself a professional programmer. If you don’t know these things, you’re a dilettante. This list includes a deep understanding of data structures and key algorithms, a little math (set theory, logic, a little statistics), mastery of analysis-and-design techniques, both process (e.g., RUP or XP) and structure (e.g., design patterns), and database structure and use (e.g., SQL). You also need to know how the hardware works.

You need this stuff even if you’re not actually using it in your work, because no matter what you’re doing, knowing this material will make your work better. How could you possibly decide which of Java’s Collection classes to use in a particular situation if you don’t know how those classes work under the covers, for example?

Knowing how to build a compiler is certainly one of the skills on this need-to-know list. Compilers are fundamental to what we do every day as a programmer. Knowing how the compiler works will let you make intelligent decisions about program structure, decisions that have real impact on the quality of our programs. More to the point, most programs have to parse input (either from a human being or from a machine) and make sense of it. To do that, you have to build a small compiler.