Planio

FEBRUARY 17, 2019

So you want a software engineering job at Facebook/Apple/Amazon/Google/Netflix? It’s every software engineer’s dream to work with one of the top technical teams in the world. So how do you get a software engineering job at one of these companies? How to build a portfolio site for software engineering jobs.

Software Engineering 155

Software Engineering Technical Review Engineering Software Review 155

Scrum.org

FEBRUARY 3, 2020

Why our brain is not built for software engineering. According to Wikipedia, feedback control is: Feedback is a process in which information about the past or the present influences the same phenomenon in the present or future. Retrieved from [link] on December 17, 2012; Gigerenzer, G. Consider a thermostate.

2002 205

2002 SCRUM 2007 2003 205

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

MAY 7, 2019

“Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 1, May 2012.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. The Future of Systems-and Software Development. Laplante, ACM SIGSOFT Software Engineering Notes , Vol.

Estimate 64

Estimate 2006 2005 2012 64

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35