You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-36Lines changed: 18 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -277,8 +277,7 @@ Sooner or later I will complete it with the relative answers. Feel free to contr
277
277
### [[↑]](#toc) <aname='patterns'>Questions about Design Patterns:</a>
278
278
279
279
#### Globals Are Evil
280
-
Why are global and static objects evil? Can you show it with a code example? <br/>
281
-
[Resources](design-patterns/globals-are-evil.md)
280
+
Why are global and static objects evil? Can you show it with a code example?
282
281
283
282
#### Inversion of Control
284
283
Tell me about Inversion of Control and how it improves the design of code.<br/>
@@ -295,39 +294,31 @@ Active-Record is the design pattern that promotes objects to include functions s
295
294
[Resources](design-patterns/active-record.md)
296
295
297
296
#### Data-Mapper
298
-
Data-Mapper is a design pattern that promotes the use of a layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself. On the contrary, in Active-Record objects directly incorporate operations for persisting themselves to a database, and properties corresponding to the underlying database tables. Do you have an opinion on those patterns? When would you use one instead of the other?<br/>
299
-
[Resources](design-patterns/data-mapper.md)
297
+
Data-Mapper is a design pattern that promotes the use of a layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself. On the contrary, in Active-Record objects directly incorporate operations for persisting themselves to a database, and properties corresponding to the underlying database tables. Do you have an opinion on those patterns? When would you use one instead of the other?
300
298
301
299
#### Billion Dollar Mistake
302
-
Why is it often said that the introduction of `null` is a "billion dollar mistake"? Would you discuss the techniques to avoid it, such as the Null Object Pattern introduced by the GOF book, or Option types?<br/>
Why is it often said that the introduction of `null` is a "billion dollar mistake"? Would you discuss the techniques to avoid it, such as the Null Object Pattern introduced by the GOF book, or Option types?
304
301
305
302
#### Inheritance vs Composition
306
-
Many state that, in Object-Oriented Programming, composition is often a better option than inheritance. What's you opinion?<br/>
Singleton is a design pattern that restricts the instantiation of a class to one single object. Writing a Thread-Safe Singleton class is not so obvious. Would you try?
315
310
316
311
#### Data Abstraction
317
-
The ability to change implementation without affecting clients is called Data Abstraction. Produce an example violating this property, then fix it.<br/>
318
-
[Resources](design-patterns/data-abstraction.md)
312
+
The ability to change implementation without affecting clients is called Data Abstraction. Produce an example violating this property, then fix it.
319
313
320
314
#### Don't Repeat Yourself
321
-
Write a snippet of code violating the Don't Repeat Yourself (DRY) principle. Then, fix it.<br/>
Write a snippet of code violating the Don't Repeat Yourself (DRY) principle. Then, fix it.
323
316
324
317
#### Dependency Hell
325
-
How would you deal with Dependency Hell?<br/>
326
-
[Resources](design-patterns/dependency-hell.md)
318
+
How would you deal with Dependency Hell?
327
319
328
320
#### Goto is Evil
329
-
Is goto evil? You may have heard of the famous paper "Go To Statement Considered Harmful" by Edsger Dijkstra, in which he criticized the use of the `goto` statement and advocated structured programming instead. The use of `goto` has always been controversial, so much that even Dijkstra's letter was criticized with articles such as "'GOTO Considered Harmful' Considered Harmful". What's your opinion on the use of `goto`?<br/>
330
-
[Resources](design-patterns/goto-is-evil.md)
321
+
Is goto evil? You may have heard of the famous paper "Go To Statement Considered Harmful" by Edsger Dijkstra, in which he criticized the use of the `goto` statement and advocated structured programming instead. The use of `goto` has always been controversial, so much that even Dijkstra's letter was criticized with articles such as "'GOTO Considered Harmful' Considered Harmful". What's your opinion on the use of `goto`?
331
322
332
323
#### Robustness Principle
333
324
The robustness principle is a general design guideline for software that recommends "*be conservative in what you send, be liberal in what you accept*". It is often reworded as "*be a tolerant reader and a careful writer*". Would you like to discuss the rationale of this principle?
@@ -469,40 +460,31 @@ In web development, Model-View Controller and Model-View-View-Model approaches a
469
460
### [[↑]](#toc) <aname='databases'>Questions about Databases:</a>
470
461
471
462
#### DB Migrations
472
-
How would you migrate an application from a database to another, for example from MySQL to PostgreSQL? If you had to manage that project, which issues would you expect to face?<br/>
473
-
[Resources](databases/db-migrations.md)
463
+
How would you migrate an application from a database to another, for example from MySQL to PostgreSQL? If you had to manage that project, which issues would you expect to face?
474
464
475
465
#### NULL is special
476
-
Why do databases treat null as a so special case? For example, why does ```SELECT * FROM table WHERE field = null``` not match records with null ``field`` in SQL?<br/>
477
-
[Resources](databases/null-is-special.md)
466
+
Why do databases treat null as a so special case? For example, why does ```SELECT * FROM table WHERE field = null``` not match records with null ``field`` in SQL?
478
467
479
468
#### ACID
480
-
ACID is an acronym that refers to Atomicity, Consistency, Isolation and Durability, 4 properties guaranteed by a database transaction in most database engines. What do you know about this topic? Would you like to elaborate?<br/>
481
-
[Resources](databases/acid.md)
469
+
ACID is an acronym that refers to Atomicity, Consistency, Isolation and Durability, 4 properties guaranteed by a database transaction in most database engines. What do you know about this topic? Would you like to elaborate?
482
470
483
471
#### Schema Migrations
484
-
How would you manage database schema migrations? That is, how would you automate changes to database schema, as the application evolves, version after version?<br/>
485
-
[Resources](databases/schema-migrations.md)
472
+
How would you manage database schema migrations? That is, how would you automate changes to database schema, as the application evolves, version after version?
486
473
487
474
#### Lazy Loading
488
-
How is lazy loading achieved? When is it useful? What are its pitfalls?<br/>
489
-
[Resources](databases/lazy-loading.md)
475
+
How is lazy loading achieved? When is it useful? What are its pitfalls?
490
476
491
477
#### N+1 Problem
492
-
The so called "N + 1 problem" is an issue that occurs when code needs to load the children of a parent-child relationship with a ORMs that have lazy-loading enabled, and that therefore issue a query for the parent record, and then one query for each child record. How to fix it?<br/>
493
-
[Resources](databases/n1-problem.md)
478
+
The so called "N + 1 problem" is an issue that occurs when code needs to load the children of a parent-child relationship with a ORMs that have lazy-loading enabled, and that therefore issue a query for the parent record, and then one query for each child record. How to fix it?
494
479
495
480
#### Slowest Queries
496
-
How would you find the most expensive queries in an application?<br/>
497
-
[Resources](databases/slowest-queries.md)
481
+
How would you find the most expensive queries in an application?
498
482
499
483
#### Normalization
500
-
In your opinion, is it always needed to use database normalization? When is it advisable to use denormalized databases?<br/>
501
-
[Resources](databases/normalization.md)
484
+
In your opinion, is it always needed to use database normalization? When is it advisable to use denormalized databases?
502
485
503
486
#### Blue/Green Deployment
504
-
Of of the Continuous Integration's techniques is called Blue-Green Deployment: it consists in having two production environments, as identical as possible, and in performing the deployment in one of them while the other one is still operating, and than in safely switching the traffic to the second one after some convenient testing. This technique becomes more complicated when the deployment includes changes to the database structure or content. I'd like to discuss this topic with you.<br/>
505
-
[Resources](databases/bluegreen-deployment.md)
487
+
Of of the Continuous Integration's techniques is called Blue-Green Deployment: it consists in having two production environments, as identical as possible, and in performing the deployment in one of them while the other one is still operating, and than in safely switching the traffic to the second one after some convenient testing. This technique becomes more complicated when the deployment includes changes to the database structure or content. I'd like to discuss this topic with you.
506
488
507
489
508
490
### [[↑]](#toc) <aname='nosql'>Questions about NoSQL:</a>
0 commit comments