Action: Print 'Hello, world!'.webp){kind=logo}
Ask the right questions to secure the right DRAKON talent among an increasingly shrinking pool of talent.
DRAKON is a visual algorithmic programming language developed by the Russian space program for use in their onboard systems. It was designed to be easy to understand and write, even for non-programmers. DRAKON's primary feature is its unique flowchart-based syntax, which emphasizes clear, readable diagrams over traditional text-based code. This makes it particularly suitable for complex systems where clarity and simplicity are paramount. The language supports both procedural and object-oriented programming paradigms, making it versatile enough to handle a wide range of tasks.
The next 20 minutes of the interview should attempt to focus more specifically on the development questions used, and the level of depth and skill the engineer possesses.
DRAKON provides a more intuitive and easy-to-understand representation of program logic. It also has a more strict syntax, which can help prevent errors and misunderstandings.
DRAKON can improve code readability by providing a visual representation of the code logic. This can make it easier to understand the flow of the program and spot potential issues.
DRAKON focuses on clarity and simplicity, making it easier to understand for non-programmers. UML, on the other hand, is more complex and detailed, making it more suitable for large and complex systems.
The key elements of a DRAKON diagram are: Header, Silhouette, Icons, and Tail.
The main principles of DRAKON are: understanding should be easy, the human brain's limitations are respected, visual syntax is used, and there is no need for a manual.
The field of programming is always evolving. A good DRAKON developer should show a willingness to learn new technologies and adapt to changes.
Most DRAKON developers will need to work as part of a team. The candidate should be able to demonstrate good communication skills and a collaborative approach.
While DRAKON is the main focus, having experience with other programming languages can be beneficial as it shows a broader understanding of programming concepts.
A good DRAKON developer should be comfortable with visual programming and be able to use DRAKON's visual language to create clear and understandable diagrams.
The ability to solve complex problems is a key requirement for a DRAKON developer. They should be able to demonstrate this through examples or during a practical test.
A DRAKON developer should have a deep knowledge of the DRAKON language, its syntax, and how to use it effectively to design and implement algorithms.
The next 20 minutes of the interview should attempt to focus more specifically on the development questions used, and the level of depth and skill the engineer possesses.
DRAKON's simplicity and visual nature make it an excellent tool for communicating with non-technical stakeholders. I would create DRAKON diagrams to represent the logic of the system, and then use these diagrams to explain the system to the stakeholders.
DRAKON is a visual language for representing program logic, while flow-based programming is a programming paradigm that defines applications as networks of processes that exchange data across predefined connections.
DRAKON is not suitable for modeling very complex systems, as its simplicity can become a limitation. It also lacks some of the advanced features found in other modeling languages, such as UML.
I would start by breaking down the system into smaller, manageable parts. Then, I would create a DRAKON diagram for each part, showing the flow of logic. Finally, I would combine these diagrams to create a complete picture of the system.
DRAKON is designed for clarity and simplicity, making it suitable for both programmers and non-programmers. BPMN, on the other hand, is more detailed and complex, making it more suitable for business process modeling.
A skilled DRAKON engineer should demonstrate proficiency in the DRAKON visual programming language, problem-solving skills, and a strong understanding of software development principles. Red flags include lack of clarity in explanations, inability to provide practical examples of using DRAKON, or unfamiliarity with basic coding concepts.
Action: Print 'Hello, world!'Action: x = 10
Action: y = 20
If: x > y
Then: Print 'x is greater than y'
Else: Print 'x is not greater than y'Action: arr = [1, 2, 3, 4, 5]
Action: arr = arr.reverse()
Action: Print arrAction: thread1 = Thread.new { Print 'Hello from thread 1!' }
Action: thread2 = Thread.new { Print 'Hello from thread 2!' }
Action: thread1.join
Action: thread2.joinAction: class Car
Action: def initialize(make, model)
Action: @make = make
Action: @model = model
End
End
Action: car = Car.new('Toyota', 'Corolla')
Action: Print carAction: def factorial(n)
If: n == 0
Then: Return 1
Else: Return n * factorial(n - 1)
End
End
Action: Print factorial(5)The final few interview questions for a DRAKON candidate should typically focus on a combination of technical skills, personal goals, growth potential, team dynamics, and company culture.
DRAKON is a visual language for representing program logic, while object-oriented programming is a programming paradigm based on the concept of 'objects', which can contain data and code: data in the form of fields, and code, in the form of procedures.
The main challenges of using DRAKON in a distributed team are ensuring that everyone has access to the DRAKON diagrams, and managing the complexity of large DRAKON diagrams across different time zones and locations.
I would create a DRAKON diagram of the program logic, which would help me understand the flow of the program and identify potential issues. I could then use this diagram to guide my debugging efforts.
DRAKON is a visual language for representing program logic, while event-driven programming is a programming paradigm in which the flow of the program is determined by events such as user actions, sensor outputs, or messages from other programs.
The main challenges of using DRAKON in a large team are ensuring that everyone understands and follows the DRAKON syntax, and managing the complexity of large DRAKON diagrams.
Back-end App Developer
Front-end Web Developer
Full Stack Developer (Java)
Full Stack Developer (.Net)
Full Stack Developer (MEAN)
Full Stack Developer (MERN)
DevOps Engineer
Database Engineer (AzureSQL)
Database Engineer (Oracle)
Database Engineer (General)
Solution Architect (.NET)
Solution Architect (Java)
Solution Architect (Ruby)
Solution Architect (Python)
AI Engineer (Python)
Sr. AI Engineer (Python)
AI Strategist (Python)
Business Intelligence Engineer
Systems Analyst
Mainframe Developer (COBOL)
Mainframe Developer (General)