/tech/ - Tech

Technology.

catalog
Mode: Reply
Name
E-mail
Subject
Message

Max message length: 8192

Files

Max file size: 80.00 MB

Max files: 5

Password

(used to delete files and postings)

Misc

Remember to follow the rules


Software Architecture and Systems Design Comrade 08/29/2020 (Sat) 01:43:39 No. 4492
One of the really neglected aspects of programming is software 'architecture' i.e. how to do overall design of a software system. Indeed even today many companies are replacing leetcode/algorithms style interviews with "systems design" type interviews or at least adding that. For leftists or open source programmers we also need to study systems design to make programs better. First book is a textbook for a grad school class on software architecture, published first 2013, and the next is a more modern (2020) book on architecture which teaches more FAANG style designs. opinions /tech/ ?
The Architecture of Open Source Applications https://aosabook.org/en/index.html Probably a lot more relevant to us than the FAANG voodoo.
>>4495 how about uploading/linking PDFs or w/e instead of linking to a click to pay link. This is a chan people are fucking poor
(370.60 KB 1920x1080 dumb too.jpg)
>>4496 Everything is there, click on the chapters to read them.
>>4498 thanks anon. We should convert these to pdfs too
(338.07 KB 627x720 1597894606965.png)
(7.15 MB aosa.pdf)
(5.20 MB aosa2.pdf)
>>4499 There's no need to convert, I built them for you.
>>4501 thanks anon. I also wouldn't dismiss the pdfs in OP as well even FAANG style architectures can be helpful
>>4492 I've worked in FAANG. It's a fucking mess. It's a meme that they hire great people there. Most are average to good devs. I've worked on projects that had dedicated senior architects that got scrapped years later because they were obviously badly designed from day 1. >>4495 Don't know about OSS, but I would expect it to be better written/designed. Good software developers/architects must remember to be suspicious of using meme architecture, like microservices and meme technologies like nosql, and meme research areas like ML. Also, re usability between unrelated projects is a fake meme (unless working in non shit languages, which is never the case). In almost all cases, readability, testability, and "refactorability", should be priority. Coupling, premature optimization, abusing OOP patterns (SingletFactoryAbstractFactoryBeanVisitor), use of compiler directives, global state, parallelization, should be avoided as much as possible. Clear APIs are also very important. But yeah, how software is made is a good idea to think of new ways of structuring code.
(48.03 KB 894x773 mmm.png)
>>4508 >I've worked on projects that had dedicated senior architects that got scrapped years later because they were obviously badly designed from day 1. thats a reason to study architecture more, not less... as for >>4495 : seriously, can any of these anons responding >NUUUUU these graduate level textbooks on architecture are wrong, every academic computer scientist and senior FAANG engineer is a pseud compared to me, read my Stallman memes instead they are way more better and based. actually tell me what particular problems with the PDFs in OP? or in >>4493 which is the pdf that has the FAANG styles, or are you literally just shitting on it because its muh silicon valley and i'm going to write it in common lisp instead because Paul Graham and Stallman told me to do that in the 90s even though the last time they wrote code 80% of the people that use this site weren't even born. Really, the fucking arrogance. >Good software developers/architects must remember to be suspicious of using meme architecture, like microservices and meme technologies like nosql, and meme research areas like ML. those things are only memes for non tech companies which would indeed be better off making traditional apps + a relational database, which in practice, they already do. Almost every non-startup/faang just does 4 load balanced traditional web app (server side rendered) with an oracle or microsoft database and some rando reporting software for the business analysts/managers like crystal reports(if c#) or Jasper reports for java. >In almost all cases, readability, testability, and "refactorability", should be priority. >Coupling, premature optimization, abusing OOP patterns (SingletFactoryAbstractFactoryBeanVisitor), use of compiler directives, global state, parallelization, should be avoided as much as possible. Clear APIs are also very important. no disagreement
>>4493 p.s. this post/book is the pdf version in which some of the images are stretched. The epub version on libgen is much better: http://libgen.rs/book/index.php?md5=71AE4AAA42B5858F370A672E2B43189B its clearly meant to be read as an ebook and not printed
>>4516 I1m sure it's real useful if you have FAANG infrastructure.
>>4508 You dont know what you are talking about, you never was in faang for sure. You cant write good Java code (decoupled) without using OOP patterns

Delete
Report

no cookies?