-
Notifications
You must be signed in to change notification settings - Fork 0
Legal and Ethical Development Specialization
Base theories from universities worldwide regardless of suggested references:
3 different specializations to eliminate the dirty business and manipulation which are done via mother fuckers thieves terrorists who steals the mental efforts of human resources and kill them later when they become old - also this way of specialization the human resource will grow steady in his/her career path, so the depth and breadth will grow up proportional with time in the proper direction besides becoming stable in his/her life and benefits his/her society
-
Senior Java Developers [Backend]
are responsible of:JD
-
Junior Java Developers [Backend]
are responsible of:JD
-
Senior JavaScript Developers [Web Frontend]
are responsible of:JD
-
Junior JavaScript Developers [Web Frontend]
are responsible of:JD
-
Senior Java Developers [Mobile Frontend]
are responsible of:JD
-
Junior Java Developers [Mobile Frontend]
are responsible of:JD
Followed pattern to define a developer: Seniority Level
> Programming Language
> Specialization
-
(Junior or Senior) Java Developer [Backend]
-
(Junior or Senior) JavaScript Developer [Web-Frontend]
-
(Junior or Senior) Java Developer [Mobile-Frontend]
-
Tools
forBackend
- Java MIN 8 to be able to use Spring-Boot and MAX 11 till the cow boys toys get investigated and vanished,
- with Spring-Boot as a Framework
-
Tools
forWeb Frontend
- JavaScript,
- with React as a Framework
-
Tools
forMobile Frontend
Hint:
: Use IDE's plugins upon need to get more functionality.
Github portfolio tips for developers
Don't be afraid if you're a newcomer to the industry. The University-education is enough, so NO need to fucken courses or certificates which means the programming constructs you had learned so far is enough to produce a fully working useful software. Just get hands-on-experience
as much as you can before joining a standalone corporate in the future.
Life Wisdom: GARBAGE IN => GARBAGE OUT π
-
Reuse the built-in functionality within the programming language and the development framework, then if there is no such kind of built-in functionality, use a library attached to the developed app as an external dependency.
-
Too much unnecessary code and libraries affects the app stability.
-
Theory is good to be reused wisely, however during development always follow the single thread model and know how to control it upon need.
-
Advice for backend developers:
- Just read about http-thread-pool which is built-in inside application server
-
Spring-Boot
uses embedded application server NOW - Unlike those old technologies which forces you to deploy the generated bytecode into an application server
-
- Just think about the code and easy configuration to get the system up an running and how it works, so you can consider
Spring-Boot
the most dominant now.
- Just read about http-thread-pool which is built-in inside application server
-
Don't go like a fucken sheep π¦ π π¦ π π· π π π π π after mother fuckers thieves who wants to make money as mad-scientists by upgrading a version without knowing the reason. The science taught inside the university is enough. Upgrading a version shall always be internally implicit because the explicit features shall be reused as long as it get exposed to the user regardless of his/her level (from 0/1 - on/off till developer level). It's nice to check how a programming language is baked inside a university before see the light π΄βπ΅βπͺππππ€².
- Bloody hell π πͺ reference to check if you got some free time mate π =>
Compiler Construction
- Bloody hell π πͺ reference to check if you got some free time mate π =>
Code is written based on a science π AKA programming and is created based on mathematics utilizing its various disciplines since home-kindergarten π‘ level not as assholes who do not know how to count-by-hand π or even 1 + 1.
So if you try learn how to code in a certain specialization β
, you should not repeat β οΈ
In real life you SHOULD know how to run a usable meaningful code via the IDE in the first not on a meat's paper π mates before generating the binary-standalone-code.
- Overview
- University Role
- Architectural Components
- Legal and Ethical Development Specialization
- System Administration
- Software Deployment
- Git Repositories | Access Control
- Testing notes - Tester [QA]
- Daily Standups
- Onboarding process upon hiring newcomers
- Tickets Flow AKA Industrial Software Manufacturing Process
- Sprint
- Legal and Ethical Aspects of Contracts
- Maintenance Deals: new contracts after delivery to avoid wasting the money of the clients and burning out the human resources
- Human Resources Planning to the Software-Development-Unit
- Possible future moves of Human resources
- Notes to Managerial Positions
- Notes for Self Study During the University Phase
- Screening Interviews
- Search keywords for recruiters
- Email-Writing
- Job advertising template for recruiters
- Ethics of writing useful software
- How to do a complaint against someone in a safe way
- Internal and external communication tools within an organization
- Necessary amount of information technology knowledge for employees before work