A complete computer science study plan to become a software engineer.
-
Updated
Jul 5, 2020
A complete computer science study plan to become a software engineer.
An ultra-simplified explanation to design patterns
Programming curricula
A best practice for tensorflow project template architecture.
This repo collects examples of intentional and unintentional hacks of media sources
Everything you need to know for a Software Engineering interview
A career guide to Front End Developers
Books for people who are or aspire to manage/lead team(s) of software engineers
Risk-First Software Development
Software architect roadmap
A curated list of articles that cover the software engineering best practices for building machine learning applications.
Programming Dictionary
A guide on how to write readable, reusable, and refactorable software
Interview Preparation material for Senior Software Engineer - Android role
Python Framework to analyse Git repositories
In this example the generated table of contents doesn't link to the sections on the page, because the headers have anchor tags in them. These should be sanitized out.
Quiz & Assignment of Coursera
A gently curated list of companies using verification formal methods in industry
These are coding solutions for problems I study while preparing for technical interviews at tech companies
A curated list of references for MLOps
A Discrete Fourier Transform (DFT), a Fast Wavelet Transform (FWT), and a Wavelet Packet Transform (WPT) algorithm in 1-D, 2-D, and 3-D using normalized orthogonal (orthonormal) Haar, Coiflet, Daubechie, Legendre and normalized biorthognal wavelets in Java.
At the moment we suppress exceptions thrown by Studies, and some exceptions thrown by CommitVisitors.
See discussion in #74.
SOLID Principles - simple and easy explanation
The most common question-patterns for any coding-interview
Add a description, image, and links to the software-engineering topic page so that developers can more easily learn about it.
To associate your repository with the software-engineering topic, visit your repo's landing page and select "manage topics."
I'm curious as to what the recommended approach is on testing operations? We've started using them and it's a good concept, but I'm uncertain whether these are to be tested as unit or functional as I referred to the wiki on testing jobs and features.
Currently one of my operations relies on a DTO passed through to it that has been processed in previous jobs. If I was to functionally test it, I