Jeff Nelson, a former Googler and inventor of Chromebook says on Quora, “One habit I've clung to is writing small prototypes when I'm trying to learn new concepts.
For example, I'll sit down with a book or a web page, and over the course of a few hours, write 30 or 40 programs all of them only a few dozen lines long.  Each program intended to demonstrate some simple concept. This prototyping makes it very easy to try out many concepts in a short period of time.”

Miguel Paraz, Software Engineering Student habit is to “keep a log in a text file or document on my work computer. Before trying to solve a problem, I write it down first. And then I describe the details as they happen.”

Writing Python in Java syntax is possible with a semi-automatic tool. Programming code translation tools pick up about 75% of dynamically typed language. Conversion of Python to a statically typed language like Java requires some manual translation. The modern Java IDE can be used to infer local variable type definitions for each class attribute and local variable.


Translation of Syntax
Both Python and Java are OO imperative languages with sizable syntax constructs. Python is larger, and more competent for functional programming concepts. Using the source translator tool, parsing of the original Python source language will allow for construction of an Abstract Source Tree (AST), followed by conversion of the AST to Java.

Python will parse itself. This capability is exhibited in the ast module, which includes skeleton classes. The latter can be expanded to parse and source each node of an AST. Extension of the ast.NodeVisitor class enables python syntax constructs to be customized using translate.py and parser.py coding structure.

The Concrete Syntax Tree (CST) for Java is based on visit to the AST. Java string templates can be output at AST nodes with visitor.py code. Comment blocks are not retained by the Python ast Parser. Conversion of Python to multi-line string constructs with the translator reduces time to script.


Scripting Python Type Inference in Java
Programmers using Python source know that the language does not contain type information. The fact that Python is a dynamic type language means object type is determined at run time. Python is also not enforced at compile time, as the source is not specified. Runtime type information of an object can be determined by inspecting the __class__.__name__ attribute.

Python’s inspect module is used for constructing profilers and debugging.
Implementation of def traceit (frame, event, arg) method in Python, and connecting it to the interpreter with sys.settrace (traceit) allows for integration of multiple events during application runtime.

Method call events prompt inspect and indexing of runtime type. Inspection of all method arguments can be conducted. By running the application profiler and exercising the code, captured trace files for each source file can be modified with the translator. Generating method syntax can be done with the translator by search and addition of type information. Results in set or returned variables disseminate the dynamic code in static taxonomy.

The final step in the Python to Java scrip integration is to administer unsupported concepts such as value object creation. There is also the task of porting library client code, for reproduction in Java equivalents. Java API stubs can be created to account for Python APIs. Once converted to Java the final clean-up of the script is far easier.

Related:

 What Are The 10 Most Famous Software Programs Written in Python?

Python, a Zen Poem

In programming, memory leaks are a common issue, and it occurs when a computer uses memory but does not give it back to the operating system. Experienced programmers have the ability to diagnose a leak based on the symptoms. Some believe every undesired increase in memory usage is a memory leak, but this is not an accurate representation of a leak. Certain leaks only run for a short time and are virtually undetectable.

Memory Leak Consequences

Applications that suffer severe memory leaks will eventually exceed the memory resulting in a severe slowdown or a termination of the application.

How to Protect Code from Memory Leaks?

Preventing memory leaks in the first place is more convenient than trying to locate the leak later. To do this, you can use defensive programming techniques such as smart pointers for C++.  A smart pointer is safer than a raw pointer because it provides augmented behavior that raw pointers do not have. This includes garbage collection and checking for nulls.

If you are going to use a raw pointer, avoid operations that are dangerous for specific contexts. This means pointer arithmetic and pointer copying. Smart pointers use a reference count for the object being referred to. Once the reference count reaches zero, the excess goes into garbage collection. The most commonly used smart pointer is shared_ptr from the TR1 extensions of the C++ standard library.

Static Analysis

The second approach to memory leaks is referred to as static analysis and attempts to detect errors in your source-code. CodeSonar is one of the effective tools for detection. It provides checkers for the Power of Ten coding rules, and it is especially competent at procedural analysis. However, some might find it lagging for bigger code bases.

How to Handle a Memory Leak

For some memory leaks, the only solution is to read through the code to find and correct the error. Another one of the common approaches to C++ is to use RAII, which an acronym for Resource Acquisition Is Initialization. This approach means associating scoped objects using the acquired resources, which automatically releases the resources when the objects are no longer within scope. RAII has the advantage of knowing when objects exist and when they do not. This gives it a distinct advantage over garbage collection. Regardless, RAII is not always recommended because some situations require ordinary pointers to manage raw memory and increase performance. Use it with caution.

The Most Serious Leaks

Urgency of a leak depends on the situation, and where the leak has occurred in the operating system. Additionally, it becomes more urgent if the leak occurs where the memory is limited such as in embedded systems and portable devices.

To protect code from memory leaks, people have to stay vigilant and avoid codes that could result in a leak. Memory leaks continue until someone turns the system off, which makes the memory available again, but the slow process of a leak can eventually prejudice a machine that normally runs correctly.

Related:

The Five Principles of Performance

In Demand IT Skills

Different programming languages gain popularity for different features.  Java tutorials have proven particular popular over a long period of time, thanks to a diverse group of strengths inherent to the language itself.  Let’s examine some of the basic elements of Java, and find out what it is both powerful and popular:

·         WORA – Write Once Run Anywhere is a programming ideal that has never been effectively achieved.  The goal is to be able to write code a single time, and have it deploy in the same way across multiple platforms.  Although it is still an ideal, proper Java tutorials exist that demonstrate how we are moving closer to success.

·         Object-Oriented – This programming philosophy designates that there is no coding that takes place outside established class definitions.  A large class library is also available right within the core language pack.

·         Compiler plus Interpreter – Once you have written your code, you can compile it into bytecodes which are then fed into a JVM, or Java virtual machine.  You can then follow popular Java tutorials to see how you can extensively debug your code using this functionality.