I started my artistic awakening in Backstage Theatre Scenography . It stirred up a deeper understanding on how motion behavior in cinetic design would give me more perspective on digital arts objects - interacting tools ( hardware / software ) and materials ( space / time elements). At the same time, I have always been interested in improving Teamwork Strategies & Communication tools to create solid ideas /projects under different cultural environments. Image and Sound foundations taught me how to look into deeper aesthetic and scientific dimensions , which inspired me to create visual-sound instalations with kinect, sensores, cameras and projector - With the rise of XR Technology products, it lead me back to computer science ( programming tools). I went back to computational art because of how it melded these interests together. Technology isn't just changing the way we work . It's also affecting the way we live and learn skills. 

At the end of the day, it's all about your journey as a person, on how you overcome obstacles in life regardless of the route constraints. Even the worst experiences can give you the strenghts to go on. The thing about stories is that they connect to your inner self or reflect as a mirror, although our singularity "beeing" is always inbetween. Life has somehow pulled me back to my technical skills - I had to learn to let go my past creative instincts, to balance between creativity and technology. - It has been a hard process to communicate , with ups and downs missconceptions. Throughout these life experiences, I worked with diverse teams . This struggle resulted into a personal / professional growth . The way I see , it's important to everyone find their opportunity to learn with each other within the project process - optimizing knowledge as a whole ; aligned and focused on all functions of the organization into creating value for the entire teamwork / businesses. For those teams that didn't work so well - I learned the hard way, on how to make it better - thinking about tools in terms of how, rather than just what, when, or why; learning with uncertainty or how to create solutions that could minimize risk and performance faults. I realized that throughout the process of learning with a teamwork, there is also a process of learning (space within us) that we ought to understand and respect towards the project success. When we work with someone we mustn't forget our place in the project even if we are in different stages in life and maturity.

As an audiovisual technician and creative content in entertainment and journalism I developed team skills - using depth analysis of the aesthetics ( media editor and camera DOP assistant ; production film - narrative plans; actor dirrection; equipment grip for TV (light /lens), videographer or FILM electric Management ) or even synchronicity through technical sensory ( auditory and visual culture, crafting brand identify - story engagement acrosss platforms / motive driven through intuitive concepts such as Content strategy ; creative branded - from concept to delivery . Having a good cross-section of team skills in software and Hardware, sparks insight and understanding on which tools and tecnology are adequate to the scale of the project and how to facilitate requisites : conversion branding; analysis or strategic planning techniques, that provides assessment tools - depending on the project requirements SWOT , so that error , security and damage issues with equipment can be minimized and productivity maximized ----> It´s important to have the ability to diagnose and solve problems that happen or could happen : " How to combine the objects of MIBs (, ) SNMP ( ,) so that they offer interesting information about the network? What are the thresholds for each interesting performance index? How to get to the problem that is occurring on the network? What are the suggestions to solve the problem? How to prevent this problem from happening again? " --- all these are questions asked by the network management teams - so I updated my knowledge in helpdesk to understand user complaints about technology features of information, either to fix problems or use tech responsibly delegating to other technicians. As a technical support team I encountered ultimately responsiblility for the network maintenance and configuration. As a network operator I practiced responsibilities for receiving the alarms generated by the management station. There is also the team manager skills, who directs and monitors the performance of team members. In work environments, It's possible that one or two people just form the team and accumulate for yourself all the papers.

Therefore, teams should evaluate the architectures of various technologies that can help ensure their product's performance. Partnerships between telecommunications companies (Internet providers), who have both broadband capacity (available for sale) and Internet customers, and owners of short film sets, who understand the issues associated with content production, quality and marketing, are ideal for the Internet movie market. In this way a company, whose incremental costs due to excess bandwidth is practically zero, can subsidize the most significant costs of providing the product. In exchange, Internet provider customers would gain access to the highly desirable streaming film content, differentiating the service provided by the Internet provider. Those Internet movie companies with the ability to partner with telecommunications companies are best positioned to succeed in the coming years. As the number of television stations and websites increases, search engines and virtual agents, especially those with the ability to search multiple media platforms (television and internet), will play an important role in the manufacture of manageable content for the end consumer. However, the ones that will achieve the greatest success in the digital entertainment industry will be those that manage to establish trustworthy brands, similar to what happened with television networks in the analogue television era.

IT technologies alike the MXF Import/Export XML based API are opening the possibility for new approaches on the implementation of digital television facilities covering the whole workflow: acquisition, creation, editing, control, storage, broadcasting, publishing and archiving of digital TV content.

Programming Software has taught me how to work with teams establishing the relation between geometry, science, light, poetry and their transformations & human interaction between software . You can still create animations with HTML5 by combining HTML, CSS, and JavaScript (JS), building shapes. Also, you can control animations and edit images, video, and audio by means of JS or CSS elements ( ex.canvas). From the tactile mirror to the virtual body with logic associations in a more understanding-objective-organized- structured - secure way : the view on computer systems from the perspective of a programmer, rather from the more traditional perspective of a system implementer ( hardware, operating system, compiler, and network -processor architecture, program optimizations, the memory hierarchy, linking control flow, virtual memory and memory management, system-level I/O, basic network programming ) ; To write better code, many Leaders come up with coding standards ( principles) and ask the programmers to follow them or add stringent code review methodologies that ensures a good deliverable product - impossible to reproduce bad code , throuthout attitudes of team members vital role for the success of the project, rather than the focus on rigid policies. Great leaders know that their leadership power comes from their questions, not their answers so don't blindly follow behind leaders always question! This inherent attitude, made me questioned on "How to deliever my work with quality effort" - furthermore , adapting into new circumstances throught consciously writing the code, respects these principles - while it ensures only the right information , so that any other developer don’t deviate in a way, that they can easily understand or continue it without much effort. ; How can high reliability and high speed be achieved? - Reducing startup latency and implementing lazy loading of certain parts of the application - How might usability trade off against security? ; How might it trade off against performance and Flexibility Sizing ? - This means , estimating the Hardware Requirements for the project ; specifically in relation to hardware capacity. Among these areas are the memory and CPU of the server (whether it’s your back-end server that has been WebSocket-enabled or a gateway that enables WebSocket traffic to flow between clients and back-end servers), and network optimization. Exploring a Component’s Life Cycle, substantially speed up interactions between the client and the server by using the WebSocket network protocol ; JSON,jQuery Ajax library & plugin integration ( Real Time Collaboration / sharing experience ) ; - Another key application of web messaging that can benefit by consuming, analyzing, and actively responding to events during the user’s browser session, a mobile device, or a desktop client application, is in the realm of machine-to-machine (M2M) communication , sometimes referred to as the “Internet of Things” (IoT), focused on connecting everyday objects to the Internet /sending asynchronous messages to build loosely coupled systems: Implementing smart meters to track and automatically report utility usage, interacting with home appliances (such as checking if the door is locked or if the oven is turned off), installing credit-card-sized capable computers (such as the Raspberry Pi), monitoring devices and moving vehicles, telemetry, and augmented reality are just a few of the use cases that M2M addresses. Most modern real-time enterprises employ a corporate services architecture as part of an efficient IT infrastructure (Enterprise Service Bus (ESB)) - Programming, also made me research on how jQuery allows you to achieve the same results while writing less code ? - ; and not assuming that a web application is secure if it’s deployed behind a firewall, because as long as there are open ports that allow external users to access a web application, one needs to invest on the application security, too ; this requires company-specific workflows, which usually need to be integrated with various internal systems, data sources, and processes (Enterprise applications ).

As a full stack developer { Front-end } & < Back-end > , I can work effectively by knowing the right thing to look up and which resources are available (resourcefulness): Provide an independent, impartial, and objective system by which a project can benefit from a total operational review - business Intelligence methods - . Throughout organization of programs as chains / reuse methods and understand how to structure, plan a set of rules / Requirements Specification techniques for undertaking different tasks of the software development process . With enough Capacity for understanding multimedia tools to adapt programming execution and value Project Planning : diagnosing the root cause of performance bottlenecks or failures and identifying areas where to tune aspects of the system for better performance on flexible and scalable project tools and frameworks.

RESOURCES FOR TRAINING | Online Wireframe Tools / Prototyping Tools

- I also trained on some Data analytics with R , Excel and Tableau : decisions on why Excel and SQL are Great Stepping Stones to Tableau and how it performes data access and analysis; You can either use Python to manipulate enormous .csv's with pandas, or take a fastest cross-platform route optimization with Tableau to extract, transform and update data visually, Creating a Storyboard Sequence : business intelligence methods and tools that connect to the server and Online cloud version, while it allows you to connect into many different data sources from relational databases, interactive dasboards to Hadoop, to data warehouses or cloud-based data services. - There are steps to design RDBMS: 1) Analyze: What your business needs for database -> 2) Draw diagram of RDBMS Model / architecture blue print -> 3) Data Collections: Including Data Type, what field is VARCHAR or INTEGER -> Then Create Table -> Then do Data Entry... 4) Use it: Write SQL Programs, Search, Queries...do what ever your business's needs. - For the Maintenance Issues, the Cloud Data Center usually provides IT tecnologies/technician that take care of the Hardware, the Network, the Backup, the Virus. This maintenance worries most people whenever using database on Local Area Network (LAN) and PCs. Web Scraping (also termed  Screen Scraping, Web Data Extraction, Web Harvesting etc.)  - and understand how to present effectively , to Demonstrate the Method's : SSADM (Structured Systems Analysis and Design Method – used in analysis and design), UML (Unified Modelling Language; a modelling notation for object oriented design), DFDs (Data Flow Diagrams) and - Soft Systems , used to elicit requirements in complex environments . I learnt to Emphasize teamwork , for teams of between two and 12 members, where requirements are likely to change - using agile approach programming methodology - a software development approach that encourages the users to be involved with the development process and anticipates the positive influence they have on requirements : such as functionality, reliability safety-critical systems, usability, efficiency / performance, supportability, maintainability and portability databases reliability, availability, scalability and recoverability (List of system quality attributes); principles of responsive design, which allow to have a single code base that will be flexible enough to render a UI that looks good on large and small screens.

RESOURCES 2020 | When one size doesn’t fit all: How to make change personal

However, the most common security dangers I encountered , fell into four main categories: SQL injection, cross-site scripting, insecure file uploads, and unauthorized access. Optimize solutions take an intelligent, automated approach to modeling, forecasting, and optimizing data center or cloud resources and cost. Automation of workflow, means spending less time working and more time making awesome tasks efficiently - improving the user experience of your website or app.

Design taught me throughout a process workflow that it depends on teamwork . Equally written on "Practices of the Python Pro" - book by DANE HILLARD : "As in fashion, art, and architecture, design in software is the process of sketching out the plans for a system so that it can be executed for maximum effect. In software, these plans help us understand the flow of data and the pieces of the system operating on that data. Planning out a software system will help you uncover areas that present risk. You can identify where sensitive user information might be exposed to a vulnerability. You can also see which pieces of the system might be performance bottlenecks or single points of failure."

I learnt to value the Anatomy of Task Time by facing issues, such as Infrastructure : Building server workstations or digital solutions ; Release / filter work pipelines ; manage computer hardware and software preparation - Environments and Access upgrades; Timely, clear and prioritised task Management :  Functional Requirements ; Non functional requirements ; Business priorities  ; Resolving Bug issues  ; Interpreting requests / feedback ; dealing with ambiguous decisions and People - absence of behaviour , conflict  , lack of response - Aware that people are not servers, they can’t be changed and reconfigured with few lines of code , within few seconds. Throughout technical documentation and all the process I projected the whole software development lifecycle - a plan for every stage . Envisioning  on how useful this can help to describe product functionality, unify all kind of project information while it enables exchange of communication between shareholders and developers such as: product requirement document, UX documentation, software architecture documentation, diagrams, QA documentation, product roadmaps, etc. Pair programming and Mob programming is also a good way of transferring knowledge. It helps improving communication and time managment, by avoiding unacessary meetings.

Fonte da imagem : Project Manager

Good decisions on bad data are just bad decisions that the company's hasn’t made yet -". Such as, Knowledge and requisites for the Requirements Elicitation, come before action ( System requirements analysis) - to help design methodology for reliable software systems and engage a constructive healthy workspace.

When analyzing consistency in a teamwork environment context: a transaction must also not break any of the constraints or rules. This actually teaches you a lot about flexibility and planning – focused on the final goal to validate congruence quality data. This attitude ensures the integrity of any project that manages growth - ideas for maximizing performance, interoperability, and reusability - to avoid troubleshooting problems .

If I were a client , I’d be very concerned about how to improve the quality of information and any communication that uses outdated technology - attending to the scale of the project - by identifying, mitigate, and managing risks, test, recovery/disaster plans, and build out systems that contain fewer risks Services and microservices ; Scaling applications , refers to the assign of services to specific teams, label the criticalness of each service, and devise failure scenarios and recovery plansCloud services; requires understanding of the cloud-based services structure , resource allocation, and service distribution .

RESOURCES | 2020: ‘You’re not going to get it all right’: IBM CMO Michelle Peluso on managing through a crisis.- "When everything changes overnight, previous assumptions can’t be trusted. And a company— its functions, teams and individual employees—must be able to pivot almost instantly to account for the new reality. Agile teams are particularly good at this, because they excel at prioritization." -

Add New Task

• To Do

  • Analysis

  • Coding

  • Card Sorting

  • Measure

• Doing

  • Hypothesis

  • User Testing

  • Prototype

• Done

  • Ideation

  • Sketches

• Trash

  • Interviews

  • Research

  Delete

Image: Using Task Context to Improve Programmer Productivity

People get overwhelmed when they try to work on big projects, without breaking it down into tasks and organize it according to requirement conditions. For most of the team members and client, it might be easier to ignore the phase if they intend to work alone, but for many makers and creatives as a teamwork that involves other people, it's the only way to see the big project and move towards your bigger goal. This is a recipe for overwhelm and feeling bad about your workday: the difference between feeling awesome or feeling awful about your workday. The task is a continuous work with flexible / parallel workflow deadlines. These are fundamental details to differentiate a project from a task. These concepts help to design methodology for reliable software systems. Documentation is needed to supplement human memory and to help organize program planning. Also, documentation is critical to communicate with others who have an interest on the program, especially those who may be part of a programming team. Since turnover is high in the computer industry, written documentation is needed so that those who come after you can make any necessary modifications in the program or track down any errors that you missed.

Likewise, synchronization of the concurrent subtasks on an overall task are not completely independent of each other : If there is no coordination mechanism, working systems cannot achieve the expected performance due to the inappropriate task execution sequence. Agile methodologies plan, track work records and simplifies the implementation of complex tasks - coordinating various itenerations throughout design, implementation, and deployment. No quality attribute is entirely dependent on design, nor is it entirely dependent on implementation or deployment. A good architecture is necessary, but not sufficient, to ensure quality. 

LEARNED LESSONS | 2020:  “If you have more than three priorities, you don’t have any.” Determining these priorities and how they’re going to be measured is arguably the most important job of a team leader because most of the work that everybody does will flow from those goals. Those priorities have to be lined up as carefully as the trajectory of a rocket launch, because even the slightest miscalculation can take a team off-course over time. " How to Build a Successful Team By Adam Bryant / Illustrations by Julia Yellow

“ Documents record decisions made and agreed upon orally; they create a paper trail. More important, the process of writing a document turns a vague idea into an explicit plan. Even if no one reads it at all, an idea written down is a decision made, a conclusion reached. If a feature of a game is not described in writing, there’s a good chance that it has been overlooked and that someone will have to make it up on the fly—or, worse, that each part of the team will have a different idea of what they intended to do.”

"When working on a large software system, a programmer typically spends an inordinate amount of time sifting through thousands of artifacts to find just the subset of information needed to complete an assigned task. All too often, before completing the task the programmer must switch to working on a different task. These task switches waste time as the programmer must repeatedly find and identify the information relevant to the task-at-hand. It's important to understand mechanisms that captures, models, and persists the elements and relations relevant to a task. Understand how our task context model reduces information overload and focuses a programmer’s work by filtering and ranking the information presented by the development environment. A task context is created by monitoring a programmer’s activity and extracting the structural relationships of program artifacts. Operations on task contexts integrate with development environment features, such as structure display, search, and change management. Report a statistically significant improvement in the productivity - documentation." in site (other lectures on System Programmer) <------ click to site

LIÇÕES APREENDIDAS | 2020: - Teamwork does not happen on its own. | 2020: 7 ways to create a culture of teamwork workplace .

Strategy is often instilled in business schools as a cascade of choices around where to play and how to win - designing different architectural model canvas gained popularity due to is simplicity and conduct focus on efficient results ( visualize the external and internal impacts ) beyond product-centric thinking or towards business model thinking, in order to deploy tasks successfully and Drive Innovation. ---> The Backbone Guideline Business Plan is the path to ensure the success of creating a project and how some experiences proceed other, although hard it may have felt to take some decisions, tend to draw more process errors into greater proportions - due to unhealthy synchronized planning - though, it's not about "failure" or "personal atacks", but rather considering a dangerous way to guarantee integrity and safeguard yourself or ensure that in the process of creating a project. I believe every element of the team can grow from a human and professional point of view - These soft skills in spite of good or bad experiences, turn evident that the #bad one's are not only an effect and cause of risk experience but most of all, an opportunity to understand that it can also teach you soft skills : on how to look to a problem outside the borders. Embedding a knowledge of risk management into the day-to-day practices increases better planning, strategy, policy and decisions. An increasing effect on the overall health and performance of your organization. Managing Risk throughout the Organization is a way to safeguard yourself by preparing for the possibility of failure or danger. Adapting the attitudes and values of the organization to become more aware of risk, means one can develop a better sense of the nature of uncertainty as a core business issue.

Everything has a deadline - No matter who you work for or how big your project, knowing what to tackle first when you’ve got lots of tasks is tough for any project manager. Project prioritization gives you and your team an understanding-follow plan for the work that needs to be done. In large-scale projects, risk management strategies might include extensive detailed planning for each risk to ensure mitigation strategies are in place if issues arise. For smaller projects, risk management might mean a simple, prioritized list of high, medium and low priority risks.

Projects “loose identity and impulse” if this is not considered at all. Projects breath and suffocate on their own, the same way as people do. Even quick responds to specific event needs to be planned and documented in a reasonable consideration. It's what determines the Quality. Knowledge and requisites for the requirements, come before action : : it is more secure for the task to already have been taken in consideration different handy backups that support technology and responsive requirements to avoid problematic situations - preventing with solutions before giving space to failure helps to engage to a constructive healthy workspace: the requisites/ management requirements for the success at work, in broader terms than skills.

A project is a temporary effort that includes multiple tasks. It is a way of organizing resource. A space where a group of individuals who are assembled to the scalibility of the architecture module, perform different tasks on a common set of objectives for a defined period of time. It also presents different phases: a beginning, middle and end . Respecting the Life cycle will Determine if a product succeed (Cost/Volume/Profit Relationships) and how each person responds efficiently and with sense of responsibility and involvement / engagement ( critic and creative thinking ). I learnt the hard way, that there are Different times on the software life cycle due to multiple entities — from design time by a developer to runtime by an end user. A binding time decision establishes the scope : the point on the life cycle - and the mechanism for achieving the variation.

Understanding how to create a software development project depends on the implementation of an organized plan: trackled and governed throughout challenging Teams . The software architect and the project manager responsible to coordinate and oversee the implementation process are crucial, because there is a need for an explicit coordination strategy ; which means they have a set of "structures" needed to reason about the system that comprise software elements, relations among them, and properties of both ( Quality Attributes Affected : modifiability; “Subsetability” ; extensibility ; Portability; performance; Interoperability; availability ; Development efficiency ) - formal methods are needed for co-located development; tradeoffs between schedule, function, and cost. The progress is usually tracked by both formal metrics and informal communication mechanisms. The issue of who has control over a particular portion of the system may prevent some business goals from being realized.

■ Deployment structure , shows how software is assigned to hardware processing and communication elements ( Module structures ;Component-and-connector structures ; Allocation structures ) . ■ Implementation structure, shows how software elements (usually modules) are mapped to the file structure(s) in the system’s development, integration, or configuration control environments. ■ Work assignment structure, assigns responsibility for implementing and integrating the modules to the teams who will carry it out.

Image Footnote : Business process management is neither task management (which focuses on individual tasks) or project management (which handles one-time or unpredictable flows). Task management is about handling or organizing a set of activities that arise out of a project.

However, writing a business plan too early—without having a fully developed product or clearly defined customers—will create very little value. Instead, refining the creative idea, verifying the market demand, and defining a business model are all critical to the process - in Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers Paperback by Alexander Osterwalder  

“Just because your product is perfect in your mind doesn’t mean others will feel the same way. If you are too eager to launch, too eager to your product on the news, it could bite you in the back soon enough.”

— INC. Magazine Online

- “5 Critical Success Factors for Early Stage Startups,” April 22, 2015

Projects need a leader who can define the work objectives and criteria for success and recruit staff from all relevant areas of expertise. The need to organize a project is most apparent when more than two departments contribute resource at the same time. Leadership refers to the ability of an individual to influence, motivate, and enable others to contribute toward the effectiveness and success of the organizations of which they are members. “Good leaders improve their emotional intelligence by making a concerted effort to understand the reasons behind an employee’s behavior. It could be a lack of trust, a bad past experience or a fear behind a bad decision. When you understand this, it’s easier to react with dignity to any type of situation.” – Vladimir Gendelman, Founder & CEO of CompanyFolders.

Image Footnote on Priority levels of issues alerts: Models are used to search for an acceptable solution. Live Maps  is a knowledge acquisition activity , that groups project structure and application-related alerts into service-oriented dashboards, that organizes what’s critical to resolve in anticipation and priority levels. The process delivers efficient, live and transparent data, enabling users to instantly see their work in process: services available, the timeframes when they can be delivered, and the costs involved in project. A comprehensive planning map also allows IT administrators to create service dependencies, or to establish relationships between applications, infrastructure components, and services. In addition to the obvious automation benefits, service dependencies help instantly identify the root cause of any problem that might occur. A map to the buildability, stability of the cycle dependencies and cohesion-security of the application / project. Software engineers also need to capture the context in which decisions were made and the rationale behind these decisions.

LIÇÕES APREENDIDAS | 2020: - Delivering an optimum quality product, be it software or hardware, is a tedious task. A product has to undergo and pass through various stages of planning, development and testing to ensure that the final product delivered is best in terms of quality and performance. Difference Between White-Box and Black-Box Testing : A Complete Guide With Techniques, Examples, & Tools

LIÇÕES APREENDIDAS | 2020: : To achieve Quality of today’s software it's expendable Software Testing, Software Validation, and Software Verification. The average software product released on the market is not error free! We need to specify the desired behavior first before project start. Software testing is essential for identifying potential weaknesses in structure of the application.

As a programmer it was important for me to understand how a project is disclosed while it helped me understand video and sound production. Building software, has been as much about people as it has been about materials or technology. Programming helps you understand computers; If you learn how to write simple programs, you will gain more knowledge about how it works. Developing a program involves steps similar to any problem-solving task: Five main ingredients in the programming process: 1. Defining the problem - the interpretation of it -: Identify User Stories ; Identify the Nouns in the user stories ; Identify the Verbs of the user stories ; This Model is the reality of the organisation : Different business will have different objects - in one company "address" might be an object and you might have "address type" (invoice, shipping, etc), in another there will be "invoice address", "shipping address" and "seller address" object, that company might need these objects as they will inherit from the base "address" object. 2. Planning the solution: Put together object interaction diagram ; Put together object responsibilities diagram ; Put together class digram UML ( shows methods, class names, dependencies, interfaces and composition , reflecting only on the most complex / interesting parts of the model; the attributes and other details will naturally emerge when coding ) ; 3. Coding the program : Strengthening your domain: The double dispatch pattern 4. Testing the program ( Accreditation versus Certification : only tools that have been tested and proven reliable should be used when processing a case. This testing procedure is known as validation ); 5. Documenting the project : both software and hardware tools /photograph the evidence, we’ll also be taking detailed notes of our actions along with any potential evidence we find , conscient that What you write in those notes matters to other people involved .~

LIÇÕES APREENDIDAS | 2020: : "Problems are obstacles and challenges that one should overcome to reach the goal. They are an inseparable part of any business, and the success of an enterprise often depends on ability to solve all problems effectively. The process of problem solving often uses rational approach, helping to find a suitable solution. "

LIÇÕES APREENDIDAS | 2020:: - How to make accountability a core part of your workplace culture | 2020

I consider myself a person that has an inherent attitude of helping others by sharing not only what I learn, but other real life experiences that inspire performances in a positive way. Since a very young age I’d been interested in cinematography , graphic motion design and poetic science : data visualization aesthetics ; algorithmic music & steganography (computer science). I found information design, motion graphics or kinetic information displays / live interactions and corpus Performances , would deliver new experiences through senses - capable of questioning tecnology beyond tool usability / functionality . I studied methods on how to interpret creatively "objects/subjects" - intersecting art with the scientific fields . As I understood how my ideas could become interactable - beyond aesthetics, I realised that the more we could deconstruct concepts apart , animate and move around to see what information can do, the more we’ll be able to push new boundaries into perspective - cross section transversely - It Allowed me to immerse through cognitive processes; analyze data and understand new media frontiers . When displayed legibly and informatively , it involves more of oursenses and/or our bodies ( Cinetic Media) . While Information technology (IT) refers to the combination of hardware, software, and services that people use to manage, communicate, and share information.

Though, we musn't forget that every learning process and creation has it's context and is driven by the nature of time and space. Meanwhile I was working on my way to make sense of all these interconnections Individually, soon I found it more difficult to explain myself when working with teams. Most of the times I had to adapt to the people around me and accept the fact that each one has their our personal journey. I kept asking : "how could I create valuable projects , where everyone had their optimal performance and learn with each other efforts?". It depended mainly on the belief, motivation and responsibility - or true dedication and trust on the project . Not everyone is willing to dedicate the same amount of energy on a project and that is extreammly difficult to manage in a team. A person can't boss force someone to work and when you feel nothing is helpfull, that can be energy wasted on team value. It also means someone will feel wasted even if the work is a masterpiece. These questions depend mostly on perception and self awareness.

This journey has been about adventure and discovery - an integrated part of my audiovisual projects ( research documentation). When I thought I was on the right path I always found new solution's elsewhere and for those reasons I have taken different roads. There is no such thing as the right linear path , as you search for inner answers, almost as a fluid movement : you are guided by your guts, affected by your actions and conscious choice impact what is born around you. With time, you learn how to listen to yourself , people and the world around you, aware that there are false steps - misconceptions , false illusion - turbulence and failures - you begin to question : even when things can be negative around us, how can we truelly discover the inner nature of ourselves in positive environments ?'.

"We cannot change our past…we cannot change the fact that people will act is a certain way…we cannot change the inevitable. The only thing we can do is play on the string we have, and that is our attitude. I am convinced that life is 10% what happens to me and 90% how I react to it. And so it is with you…we are in charge of our Attitudes.” ~Charles Swindoll

Working on the projects helped me to take ownership of my responsibilities of any updated task and make sure all the relevant information is provided . What I have learnt after being involved in different projects besides the technical hard skills, that can be useful when in relation to my personal - professional soft skills where Innovation is the key , and Optimization is required:

My projects allowed people to immerse through cognitive processes, as I analyzed data and understood how new media frontiers worked and displayed legibly and informatively - I understood how it involved more of oursenses and/or our bodies ( Cinetic Media) - inducing new levels of “presence” than traditional media. Technology has a cultural history ( a past and future story ) that goes far beyond the promising solution. Despite the ideology of technological revolution centered on trying to make people believe that it is possible to solve any problem : be it of a social, economic or political nature, with a good dose of technology, putting the user in a passive position - represents a quick and generic answer to any type of problems with Computer-aided design, telecommunications, and other developments, that have important consequences for business, government, and the labor market. This is what concerns me as a human and a creator: that we stop thinking about the problems themselves, just to worry about the solutions that encode a process in which ideas are conveyed and translated into a code or a set of symbols without analysing the ethical consequences.

On the one hand, I recognize that technology does not solve problems on its own - blindly - , on the other hand, I believe that it can be used to solve problems in a certain category, regardless of the potential for progress that this may represent that can make perfect sense because they are based on the coherence of human inconsistencies, and not on the mere logical coherence of technology.

Furthermore, I emphasize that it is necessary to define the problem , so that it is solvable as a flexible plan and doesn't create a larger one . I also realized that most Clients don't know what they need until the moment we show them Prototypes - because they need the right space to distance themselves from the project , and find time to visualize the idea -. At this point, is where I come in, with knew creative ideas: to consolidate feedback from clients, I stay up to date on the latest design , language / perspective and prototyping tools, testing them shortly after they launch, because I believe that choosing the right prototyping tool – Design + Sketch makes all the difference to succeed in work process. However, If it were neutral - technology would have no power to solve problems. Technology does nothing alone because it's interconnected - instead of fast, inconsistent solutions , as a programmer and creative I worry about questions. The production, distribution and disposal of technology, already involve a series of human actions that can be held responsible. Among these actions, I highlight the technology design actions which is when the intentions behind the technology are defined. In fact, it is necessary to invert the fundamental questions around a problem : " What trouble can technology create? How will the solution be problematized - is it Ethical ? Who will be excluded by the solution of the problem? What can be given as a guarantee of responsibility? " Technology does not solve anything - People solve it. However, people also create as many problems as they solve.

Throughout this road , I found hard time figuring out what was the right communication to each situation because context changes the perspective over reality. Time taught me how to accept the fact that , what lacks proper hierarchical structure needed for learning a subject - matter thoroughly, and could lead to your being stuck quite frequently. In short, the deeper you go - more courageous responsibility it takes, because each action has its energetic - vibrant effect that will amplify your perspectives on your ability to know exactly what to say, when to say it, and how to make it count. , to continue your personal journey :

Changing The Way You think with Time-tracking tools that everyone is comfortable to use, diminish the project cost ; estimates and forecast schedule objectives ; generates valuable insights & feedback to solve roadblocks; Leverages lessons learned to advance; syncs resources towards a reliable comprehensive career depth and transparency ; The Project Plan helps to understand how time was spent on one task , compared to what was planned ; it filters and optimizes performances that value knowledge-sharing strategy with objectives that should be specific, measurable, attainable, relevant and time-bound or focus on customer expectations, satisfaction and quality that weigh against the impacts & rebalance the dynamic relationship of constraint models of time, cost and scope as well as Schedule , Budget, Benefit and Risk , legitimate additional variables , capable of handling change requests along the way. Everyone (project managers / team / clients) will still try to control all 3 constraints by sacrificing an implicit constraint: Quality. Though, sacrificing quality to accelerate delivery tends to backfire much more quickly than expected, because it affects our ability to continue, maintain and change. It is easier to coordinate knowing that someone will deliver at least a minimal version scope by a particular date, with the possibility to improve , than knowing nothing capable of coordinating problems. Projects cannot be cheap, comprehensive, and fast all at once, so the " we" as a team , have to know priorities in order to decide, adjust and be aware what’s the essential decision making and create a detailed work breakdown structure— accurate time that estimates and track team hours to make sure you’re staying on Schedule for each individual Task.

-- Very technical workers have hard time with creatives. Ironically, what makes something creative, requires less of mechanical technical responses and more flexible working . Turning job results into productive products, only happens if combined with the required notion of balance. Since we are human beings - not robots, it's wiser not to "kill" the creatives, because they're not the threat! Otherwise, move or inspire others on the team - transfering their own interconnectedness value chains; taking advantage of technologic resources ; mapping good ideas - that aren't built on top of very identical blocks of repeated gatherd information - already known results / solutions . Also, this isn't an excuse to "skip steps"/stages of a project, to justify content Creation . I believe that In software engineering people are the hardest to work, but the most important thing that can be invested, especially team leaders, - even before you fixate on agile concepts and technology. Good team leaders work with their teams to implement permanent solutions to these problems based on 3 factors : Wait Time - for developing knowledge that you don’t have, decisions that you haven't yet made while you wait for someone else to complete their work before you can start yours; Disruption Time - expedite, organize rework, team / corporate interruptions and personal health activities ; Task Time - getting work done ; Leaders assign work depending on the Lead Time of tasks to remove as much Wait, Disruption and Task Time from overall delivery process. This actual Task Time is made up from 8 factors which are dynamic: Volume of work ; Dealing with the Unknowns - identifying unpredictable stuff that weren't consider when you were estimating the work. Complexity - figuring out an algorithm to solve a problem. Risk - testing you have to do, given the risk level that is acceptable for the task at hand. Skill  improving - your hard/soft transferable skills (programming, math, architecture, algorithm design, management, etc) or using your existing skills to get work done quicker. Domain  gaining - new domain knowledge (in some new langugage, technique, HR, Logistics, etc) or upgrade your existing domain knowledge to get work done faster. Attitude - to perceive your work environment and tasks. Aptitude - developing predisposed skills towards the work that you are doing.

Compared, Software design and programming have a lot in common with the arts, due regard for particularities. There is a need to investigate code to find patterns and design patterns movements - but also, other types of techniques that can be developed by reading code; focused on discovering and documenting reusable solutions to problems , common to software development - such as Design patterns, that formalize the study of existing codes , making the practice accessible to a large number of software professionals .

if (problem is sufficiently simple) {

Directly solve the problem.

Return the solution.

} else {

Split the problem up into one or more smaller

problems with the same structure as the original.

Solve each of those smaller problems.

Combine the results to get the overall solution.

Return the overall solution.

}

It's when things go out of hand and out of control that we realise how important it is to find structured plan so that one can learn with our mistakes in time before making a larger one and avoiding more problems that are time consuming and don't bring any real "growth" or "value" to the project identity / brand.

Programming depends on our capacity to question and not assume "something is just because". It's almost a philosophical vision of science. I understood in between eventual analític and logical errors, how to look at Availability tactics : Detect Faults; Recover from Faults ( Recovery or repair - Reintroduction or Software upgrade) Prevent Faults ; A failure occurs when the system no longer delivers a service that is consistent with its specification; this failure is observable by the system's users. A fault (or combination of faults) has the potential to cause a failure. While shifting technologies or business models , You often don’t know what you don’t know, and you have to learn as you go - Creating a culture that simultaneously values learning through failure and outstanding performance is difficult. The sooner we can discover software failures, the more robust it will become. By Questioning the meaning of every process and how things work or how to create solutions, I've learnt the true value of "consistency" in the same perspective that it's properties enables transactions that cannot break the integrity rules of a database or software performance. Consistency determines rather a potential client decides to stay with contract or walk away towards other services. Even team workers don't like to be deceived - meeting objectives with the basic principles / expectations toward a service -.

The project manager is like the conductor in an orchestra who guarantees an optimal performance of the team. When organization is neglected , this is what happens: - #1 -No clear deadlines (apart from the delivery date): "Every one of us had not an exact picture of what all the other members were doing"; "What were the milestones of the project? For what day? And what features should be dropped if we were late for a milestone? This was not much clear"; -#2 - No coordination between the teams: "Every one of us had not always a clear list of his tasks." "Sometimes I had to understand what I had to do by reading various chats, were all that was to be done was scattered a bit here and a bit there in conversation with other people"; "We had no clear idea of the timing since day 1 ". - #3 - No one has a clear overview of what is happening and can make all people work as cogs of a big machinery: "We didn’t always know who should we refer to if we had problems with something";

The distancing of vision between team members is dangerous for the project.

Image source: TOOLKIT | 2020 : Improve Your Business Modeling with a PDF to Excel Converter

The same way that when you build a network without planning, you end up with a big mess—wires running every which way, wires connected to who knows what? - Problem management, can be either reactive or proactive. Reactive management occurs when problems have already caused incidents and steps must be taken to resolve the current incident and prevent future incidents. Proactive management includes solving problems before they are noticed by service users (i.e. before they cause incidents), as well as activities such as auditing code to find bugs.

Have you ever wonder why some projects seem able to make huge changes and still ship promptly, while others collapse under the weight of their own code? - How to Identify and track risks on the project - performance evaluation and programming Language Synchronicity : Project risk management, is the process of identifying, analyzing and then responding to any risk that arises over the life cycle of a project to help the project remain on track and meet its goal. Risk management isn’t reactive only; it should be part of the planning process to figure out risk that might happen and how to control the project, if it in fact occurs. It's what will make future resolutions be possible for growth management. It's wiser to involve entire project team together, some clients representatives on the project, and perhaps some other vendors who might be integrating with your project. Get them all in the room together and do a risk identification session. Issues will inevitably come up, and need a mitigation strategy in place to know how to manage risks on the project. If there are ambiguous intention, than people will assume it's just a temporary strategic attitude that will put their person at risk or not to be taken seriously, because the intention to create value appear to be all superficial like an iceberg. Testing detects faults in the system, including those introduced during changes to the system or its requirements. Testing activities include unit testing, integration testing, and system testing. Risk-based development attempts to anticipate surprises late in a project by identifying the high-risk components. Issue-based development attempts to remove the linearity altogether. Any development activity—analysis, system design, object design, implementation, testing, or delivery—can influence any other activity.

RESEARCH | 2020: - Defect Severity And Priority In Testing With Examples And Difference

OPINION | 2020: Risk Impact/Probability Charts / Learning to Prioritize Risks

Computer programs are all about receiving, manipulating, and returning data. It will have you worry about the differences between one graphics card and another ; Privacy Issues = Trust Issues that make you think like a data scientist ; analyzing scientific data and whether the computer is connected to a network through Ethernet or wireless [ Customer and employee analytics ; Product and device analytics ;Network and operational analytics ]. Computational thinking is to understand what happens when you’re programming ( this takes years of research and transformation). Being self-taught means a lot of searching and training - by seeking out broad influences that expose you to new ways of thinking. Understanding computer languages and algorithms is a continuous struggle of trying - failing ... coffee.. and repeat...failing harder and failing better is all about learning code. If it's 4 am and you're still trying to figure out some code, than you might consider yourself a coder lover without even noticed how you become this way in the first place - addicted to the power of creation. Many programmers learn through experimentation, looking at others’ code and working out what method is best for a given situation.

LIÇÕES APREENDIDAS | 2020: "You see people being very optimistic about what they can offer in a short period of time, especially in companies that move quickly," says Alan Zucker, founding director of Project Management Essentials.

LIÇÕES APREENDIDAS | 2020: Emotional Intelligence Has 12 Elements. Which Do You Need to Work On?

Becoming a programmer isn't just about learning the syntax and the concepts of a programming language or Measuring Network Complexity aspects —state, speed, surface, and optimization— : it's about figuring out how to use that knowledge to make programs. It's a time consuming learning process. To a point that most programmers are stereotyped as antisocial hermits, but that is not a linear categorical. The only time I'm antisocial is when I hibernate into my spaceship to create / implement something. The programming activities can be solo activities, but a programmer typically interacts with a variety of people. For example, if a program is part of a system of several programs, the programmer coordinates with other programmers to make sure that the programs fit together well. You might also have coordination meetings with users, managers, systems analysts, and with peers who evaluate your work-just as you evaluate theirs. The hard parts involve dealing with clients, peers, and managers, staying productive, achieving financial security and so on. understand things that can go wrong in software development.

Computer systems have many layers, and each one depends on the layer underneath it to support.

LEARN | 2020: CODE ACADEMY

TOOLKIT | 2020: OnlineFreeTools

BOOKS | 2020: Learn To Code Together

BOOKS | 2020: Learn Code The Hard Way 

BOOKS | 2020: FIND THE BEST PYTHON BOOKS - Updated monthly!

Self-taught experiences stimulate autonomous solutions. When you teach yourself, your cognitive load doubles because it commits the information to memory and requires some kind of structured mental plan and practice until objectively know your strengths and weakness's. I´m Continuous learning new skills, either in Motion Graphics or programming web languages (JavaScript- three.js / OpenGL / WebGL) in order to integrate and create more interactive and creative VR and AR projects -. It's not something that is taught and repeated at school, but only comes into place with constantly staying up to date research , comparison data analise and practice - creating projects. It takes time consuming to create and to complete planning / process that demands documentation : The importance of complete and accurate documentation can’t be overstated. The old saying “if you didn’t write it down, it didn’t happen” are truly words to live by in this industry ; but also, discipline, in between creativity and guts to fail better; Above all persistence - Qualities I value and makes me valuable.

"People still argue about what programming is: mathematics or engineering? Craft, art, or science? We certainly argue—often with great vehemence—about the best way to do it: the Internet overflows with blog articles and forum postings about this or that way of writing code. And bookstores are chock-a-block with books about new programming languages, new methodologies, new ways of thinking about the task of programming. " Peter Seibel

In Nature, In Code teaches programming in JavaScript by implementing key concepts in biology (natural selection, genetic drift, epidemics, evolution of cooperation, etc.) everything runs on the browser. - While the web was developed, the early HTML language has evolved dramatically. A good web page experience typically involves more than just HTML. One of those ways to add more interactivity is via JavaScript. Great code is readable, bug-free, and maintainable.

RESEARCH | 2020: Augmented reality meant augmented humanity.

RESOURCES | 2020: From CG VR production, to 360 video, live streaming and post production.

RESOURCES | 2020: Drag-and-drop interactive digital elements, including video messages, music clips, interactive photo , Web and social network links, and much more!"

Everyone loves stories to which they can relate, so If you’re curious about life as a programmer than Coders at Work is the book for you. The author, Peter Seibel (a programmer turned writer), collected interviewees to open up about the famous projects that they worked on and the inspiring stories behind them. Coders at Work gives a peek into what makes some of the greatest programmers tick and how they think.

The author of Zero Bugs spent two years researching every bug avoidance technique she could find. This book contains the best of them! It includes useful tips and techniques, and presents information in an easy-to-digest way and brought to life with stories and metaphors that make it a really enjoyable (and memorable) read.

" If you've ever spent hours renaming files or updating hundreds of spreadsheet cells, you know how tedious tasks like these can be. But what if you could have your computer do them for you? " - In Automate the Boring Stuff with Python. "Step-by-step instructions walk you through each program, and updated practice projects at the end of each chapter challenge you to improve those programs and use your newfound skills to automate similar tasks."

RESOURCES | VR BOOKS : Avatars at Work and Play - Collaboration and Interaction in Shared Virtual Environments - Schroeder R., Axelsson

"Designers have developed a number of techniques to avoid being captured by too facile a solution. They take the original problem as a suggestion, not as a final statement, then think broadly about what the real issues underlying this problem statement might really be (for example by using the "Five Whys" approach (the cause-and-effect relationships underlying a particular problem ) to get at root causes). Most important of all, is that the process is iterative and expansive. Designers resist the temptation to jump immediately to a solution to the stated problem. Instead, they first spend time determining what the basic, fundamental (root) issue is that needs to be addressed. They don't try to search for a solution until they have determined the real problem, and even then, instead of solving that problem, they stop to consider a wide range of potential solutions. Only then will they finally converge upon their proposal. This process is called "Design Thinking."

– Don Norman, Rethinking Design Thinking.

In a world where everyone wants to be the first - Responsibility is an essential element of integrity - but also the congruence of what you think, what you say, and what you do. These qualities allow the team to promote the efficient sharing of vital information to improve understanding. For me, Ethical integrity is essential to promoting a healthy collaborative environment among the project: To assure trust and product quality.

My journey as a Technological adventurer was almost a self discovering journey. It has not been an easy one - but I did always stay understanding and persistent; It's important to respect everyone involved in a Teamwork , to help others also succeed is a gratification besided contribution to project value. Human qualities matter: So, I try to reach every person in it's essence , letting them be themselves ~ Also, facilitate hardware and software knowledge - human and technological resources that make something reliable and with conditions to work take place and time for oneself to grow as a human and professional - giving enough space to express full potential honestly and room to live a life with dignity - I prefer opt-out In feeling valuable by creating a value that I understand and not feel used by a disrespectful systems. I also think It's important for a team to be organized and understand how they can help one another by assuming organization as a form of respect towards other coworkers life , time and productivity -. into a state of working synchronously.

Humility, is accepting the divergent thinking and look for bridges of contact or understanding; sharing knowledge in a constructive way. My curious Nature leads me to continuous studying new skills to improve my perspectives on life as a creator, and not because I feel above other. As a Perfectionist, I learn with my mistakes ( looking in perspective). Also, try not to be only surrounded by people who feed my vision - aware that it may cause a self-induced blindness - perception of reality. I respect different cultures. People are composed of a universe of experiences shaped by its context among other factors: such as Perception, memory and action , that are all part of the same integrated system. We remember experiences that have meaning to ourselves, in order to make future predictions by matching current perceptions to those past experiences. We are better at recognizing things previously experienced than we are at recalling them from memory . Meaning comes from predictive ability, emotional salience and context. Our senses help us create meaning, but they are far from perfect.

I also learnt by trying new approaches based on intuition and sensibility - creative thinking. In most cases, people who try new approaches - combining technical and artistic - are likely missunderstood for a while, even if after a period of maturuty cycle phase they tend to reflect their valuable essence. Most of my audiovisual projects try to research & deconstruct the meaning of ""error"" and ""improvisation" assessing the ability to question and deconstruct knowledge towards new ramifications. A musical performance or dance is improvised if the actions (sounds, gestures, movements, etc.) does not result from executing a predetermined action (a rigid musical score) but is rather invented “on variations of the spot.” If performers lack this sensibility, they can only repeat stereotypical, practiced patterns. Without preparation as a precondition improvisers could not properly cope with the unexpected situations that emerge during a performance - As each situation calls for a specific response, it requires a specific adaptation and thus development of the skills that have crystallized into behavioral habits. Improvisers are at once knowledgeable and destitute of knowledge - but reworked through improvisations. Nevertheless, performing a skill also involves constantly (un)learning because concretely dealing with specific and unforeseen performing situations has a recursive effect on the development of the “know-how” of improvisation. Having a specific know-how is not only a precondition of the practice but is (re-)shaped by improvisational practices that, in this way, put into play their own preconditions - free to react to what they are confronted with in the course . The way performers cope (more or less successfully) with the (more or less) unexpected situations of each performance retroactively contributes to the (trans)formation of their skills. Each concrete situation in which a certain skill is applied is specific and cannot be anticipated. For me it's not about doing what it takes for the money, without thinking about the consequences. Responsibility is more about overcoming obstacles to become a better professional and germinated human being. It's also important technicians understand the requisites of their workplace to potential their equipment , so that error and damage issues with equipment can be minimized and productivity maximized.

“TRANSFORMATION ISN’T JUST A PROJECT. IT’S SOMETHING THAT MUST BECOME A PART OF AN ORGANIZATION’S BEING. THAT MEANS PUTTING A CULTURE IN PLACE SO THAT TRANSFORMATION BECOMES A NATURAL WAY OF WORKING.” GEORGE WESTERMAN, MIT SLOAN.

OPINION | Employee Emotions Aren’t Noise — They’re Data : Emotions provide insight into what motivates people and how to improve performance.

I believe it's important to be honest so that everyone can have space to be their "productive selves" as they work with the right tools to grow avoiding ambiguities - managing change. Delegation is a form of responsibility - it must come in use as a trust element between coworkers - understanding that every task has it's own complexity and is time consuming experience. Distractions to the obligations can cause a reflective bad effect on the quality of the work and sometimes can be overwhelming - exhausting & corrosive. All employees - at whatever level they are - should have the chance to understand each other work; even achieve mutual success in a win-win game . Effects and outcomes have causes and consequences to the project. in my point of view human element is more effective than the artificial. Time , organization and management are important keys for a project success and if everyone stays true to it's personal goals and the company values, things will work out synchronously with less overwhelming and anxiety. This is essential for reciprocity, trust, and for maintaining symmetric relationships. It also helps to join together the right people and stakeholder for a project. It's a road to create value.

“Integrity matters in three ways: leaders with great integrity foster critical trust amongst colleagues and direct deports, and demonstrate a commitment to moral and ethical behaviors. Leaders who do NOT value integrity will not gain the trust and buy-in of their teams and colleagues, which will negatively impact engagement and performance. And leading with integrity doesn’t mean never making mistakes, but recognizing and owning them, which leads to continual self-development, and demonstrates humility to others" -Jenna M. Rosenberg, Assistant Vice President, Human Resources at Vision Federal Credit Union