9 ms·
Author here, writing this book was one of the hardest things I've ever done, and there is seemingly no end to the small issues I've faced (both writing and tech
by mixmastamyk 10y ago
Author here, writing this book was one of the hardest things I've ever done, and there is seemingly no end to the small issues I've faced (both writing and technical). Would appreciate some feedback to make it as good as it can be, AMA thanks.
- nickbauman 10y agoThe separation of design and construction into phases is a hangover from civil engineering. It has the baked in assumption that the design phase is relatively cheap, short and somewhat unpredictable the construction phase is expensive, long and predictable. The root problem is the assumption that specifications can be validated for correctness, like a blueprint for a bridge can. Nothing could be further from the truth. This is a persistent myth in software development.
- HenryTheHorse 10y ago> the design phase is relatively cheap In my world (enterprise software), the design phase is usually the most expensive phase, as it tends to be staffed with expensive architect/designer/technical lead-level folks.
- mixmastamyk 10y agoYes, it is often (mostly?) true, but not always. In the book I've tried to not give the idea there is only one way to do things. Even so, a few have commented that they've got that impression. Also, from a practical standpoint, both the design and construction chapters are huge, so combining them doesn't seem to be a good idea. Perhaps I could add your warning though, if you don't mind me quoting you.
- nickbauman 10y agoI upvoted your comment even though (as a generalization) I disagree that these chapters should even exist as such. If were truly honest about the civil engineering metaphor as it applies to software, the design of a system is indeed the source code. The construction phase is done by the compiler. So your construction chapter should be about compilers and interpreters. Your design chapter should be about the explication of the stakeholder's intent in the form of human-readable code: the source code itself. What do you think?
- mixmastamyk 10y agoHmm, you've blown my mind. I've used traditional metaphors to describe and organize, such as the sdlc and topics like construction as defined by books like Code Complete. In other words, about/around these topics, not strictly limited to their concrete form or process. I suppose it isn't the only way to look at things, just common. Though we are approaching the philosophical realm at this point… reminds me of the section of Philosophy class where you learn to question if you can even trust your own senses. I'm not sure, however this is a book for beginners, and I sit on the shoulders of those that came before. Not sure I'm qualified to reimagine software engineering from the ground up as you describe. If you write that book, I'd read it!
- lifeisstillgood 10y agoTry Jack Reeves from 93: http://www.mikadosoftware.com/articles/thecodeisthedesign http://www.mikadosoftware.com/articles/thecodeisthedesign I am also writing a "this much I know" style book, and would be very interested to hear your trials and tribulations I am very impressed you got from pile of notes to finished product - bravo.
- mixmastamyk 10y agoThanks, don't do it! Unless writing comes to you easily? The most depressing thing is "finishing" the book and then have to spend a month hacking css and build scripts to work around kindle bugs and the fascists at the ibooks store.
- agentultra 10y ago> The root problem is the assumption that specifications can be validated for correctness, like a blueprint for a bridge can. We can validate specifications for correctness with automated theorem proving! The least we can do is model-checking. At least for the hard algorithms and core system interactions. We've had this ability for decades. The problem with software development is that we get all hand-wavy about "architecture," and "design." I try not to physically groan when someone starts sketching out a box diagram. They're fancy pictures, sure, and useful at a conceptual level... but the reality is that the software will look nothing like that diagram. And there's no way to check that the diagram is even correct! Useless! It doesn't have to be painfully slow, burdensome, and expensive to employ these tools either. Contrary to popular belief it doesn't take a team of highly trained PhD physicists to build a formal mathematics for modelling computations these days. There are plenty of open-source tools for using languages like TLA+ that work great besides! Ask Amazon -- they published a paper about it. Watch Leslie Lamport - Who Builds a Skyscraper without Drawing Blueprints?: https://www.youtube.com/watch?v=iCRqE59VXT0 https://www.youtube.com/watch?v=iCRqE59VXT0
- 2muchcoffeeman 10y agoI draw pictures because I think in pictures. I just took a short look at TLA+ and read a tutorial. Don't think I could use it without drawing a picture.
- agentultra 10y agoDrawing a picture is a perfectly valid and legitimate start. However I think there are many problems where a picture is not sufficient and it's necessary to have good, reliable mathematics to sketch out our designs and prove properties of them. A sketch is still useful the the absence of nothing else. But we don't build bridges and skyscrapers that way so why is it good enough for our data-centres and applications? I don't think lives have to be on the line in order for software to be considered harmful if not built correctly. There are plenty of problems where having a thoroughly checked design will save you plenty of headaches and afford you many more opportunities.
- amelius 10y ago> The separation of design and construction into phases is a hangover from civil engineering. Yes and it is a pretty good principle. The last thing you want in a software project is a design which changes all the time.
- nickbauman 10y agoExcept a design that doesn't change after a certain arbitrary phase of a project simply guarantees your best outcome will be to deliver what the customer said they wanted once upon a time.
- RubenSandwich 10y agoFirst off great job, it looks like you put a bunch of hard work into this. One area for improvement is the images. Currently some of the more information dense ones are hard to read at small sizes and clicking on them does nothing. Perhaps expand them to full size on a click?
- mixmastamyk 10y agoGood idea, thank you. In the meantime, you can right click and choose "view image" in your browser. Edit: have linked several dense images, thanks.
- mixmastamyk 10y agoI had to back this out because of a conflict with the filesystem layout and strict epubcheck by itunes. :( Sorry. I did expand the dense image in the introduction to 100% width, which hopefully helps.
- daveslash 10y agoOnly have skimmed it so far, but it looks great. Will look more soon. Off the bat though, I was looking at it on Amazon and the 'look inside' seems to scrunch up some of the text. Not sure if this is something an author can do anything about, but wanted to make you aware. I'm viewing this on Windows 10, Chrome 51, normal zoom level, and with minimal plugins. Screenshot: http://imgur.com/uXuELxv http://imgur.com/uXuELxv
- mixmastamyk 10y agoYes, I've seen this :-( thanks. Also Amazon currently doesn't handle the .svg images correctly, I have no solutions unfortunately, despite lots of googling. If anyone has any tips? Btw, besides the .svg problems, the kindle version looks fine otherwise on my iPhone, it is not squished, if that helps any.
- machinshin_ 10y agoChecked out PrinceXML?
- deleted 10y ago[deleted]
- NuDinNou 10y agoWill there be a PDF or an ePub version for this?
- mixmastamyk 10y agoYes, the version on iTunes is an epub. But they are not happy with the links to Amazon so I will have to remove them and put it back up. That will take a day or two, sorry. A pdf of the full book I'm not sure about yet, should I be concerned about copying? I'm new to authoring.
- ewittman 10y agoAlso look to localize. Some countries actually value purchasing a book over the software referenced (e.g. China) and you can make more $ that way.
- deleted 10y ago[deleted]
- Fargren 10y agoDISCLAIMER: the following is my personal belief, and I don't have more than a few anecdotes to back it up. You shouldn't be concerned about copying no matter the format. Almost anyone who gets a copy of your book illegally is someone who would not have read your book at all if he couldn't have gotten it for free. And with these people, you are better of if they do get it; they may share it with someone who will become a customer, or they themselves may become customers in the future, when they learn that they like what you do and/or their purchasing habits change.
- znpy 10y agoCan confirm: I usually "evaluate" books before buying them. Some books are really worth having on your bookshelf.
- KevinEldon 10y agoGumroad has a feature called PDF stamping [1] that puts the buyer's email address on the PDF. It's not perfect security, anyone who wants to ignore your copy rights probably will, but it might deter unthoughtful sharing. Also consider a team/company license priced at some multiple (15x?) that will allow a manager or lead to buy your book for their company/team without having to worry about violating copyrights or managing buying the book for every employee. [1] - http://blog.gumroad.com/post/40614820182/introducing-pdf-stamping http://blog.gumroad.com/post/40614820182/introducing-pdf-sta...
- ap22213 10y agoWow - nice job! I just skimmed it, but it looks great - will read more later. With all the superficial, error-ridden, and rambling books being published these days (packt, etc.), it's a pleasure to see something information-dense, accurate, and also high-quality.
- tootie 10y agoJust looking at the intro and I see SDLC and cringe. Is this still applicable to agile practices?
- mixmastamyk 10y agoYes keep reading, it teaches you the "hard way" by starting at the beginning and moving forward. Try Ch. 7 - Models and Methodology, to skip to Agile.
- TickleSteve 10y ago...and very likely, in a few years time... people will see 'Agile' or 'sprint' and cringe.
- mixmastamyk 10y agoAnd some are already cringing… I believe there have been a couple anti-agile posts here in the past month.
- TickleSteve 10y agonot unjustifiably either... Agile has been so oversold, theres a big backlash against it coming....
- superuser2 10y agoWe'll cringe at the names, sure. I'll be very surprised if we actually go back to merging, integrating, testing, and releasing code once every few months/years instead of hours/days.
- p4wnc6 10y agoContinuous delivery is orthogonal to any particular management ideology. There's nothing inherent to Agile that relates it to continuous delivery. You could interpret the Agile principles for the sake of delivering once a year releases if you wanted. And many firms do continuous delivery for very critical products and services without using Agile nor anything even remotely like Agile.
- perlgeek 10y agoKudos for tackling such a huge range of topics! As a proponent of Continuous Delivery, I found the part on releases a bit old-fashioned and slightly disappointing. I can elaborate a bit more if you want, but most likely you're already familiar with the more iterative and automated approaches. Everybody has their pet peeves, I guess.
- TickleSteve 10y agoYou're thinking too much about web and desktop software. Software is often delivered with hardware or other services which have to have releases, hence releases are still very much a thing. software world > web software.
- mixmastamyk 10y agoYes, it tries to be useful for all types of software. Iterative/incremental is covered in chapter 7 under "gradual development." CI/CD under Construction and Quality. Also, to help understand the new, it helps to know the "old." At least that's what I thought. A number of people are mentioning it, so perhaps I shouldn't have ordered it that way.
- mixmastamyk 10y ago> I can elaborate Yes, if you don't think the discussion in Ch. 7 is adequate.
- nickpsecurity 10y agoThis comment... https://news.ycombinator.com/item?id=12081603 https://news.ycombinator.com/item?id=12081603 ...was meant for you. I knew you were in the thread but wrongly assumed you submitted the thread itself.
- danso 10y agoThanks for writing and sharing this. It's not something I dived into deeply so feel free to ignore my opinion. But the main thing I feel this book lacks is a "show don't tell" mentality. I haven't read the content close enough to judge how insightful the technical nuts and bolts are. But one thing I learned only after working in software dev is the human aspect behind the pace and rhythm and success of projects. It's not just code and processes, but why such processes were implemented a n the first place. I'm violating my own principle, so I'll give an example: the book, Enterprise Rails, opens with a chapter titled, " The Tale of Twitter". Here's an excerpt: https://dan.chak.org/enterprise-rails/preface/ https://dan.chak.org/enterprise-rails/preface/ > Because Twitter was the largest, most public Rails site around, its stumbles were watched carefully, and the steps Twitter took to alleviate its scalability issues were thoroughly documented online. In one instance, the database was becoming a bottleneck. In response, Twitter added a 16 GB caching layer using Memcache to allow them to scale horizontally. Still, many queries involving complex joins were too slow. In response, the Twitter team started storing denormalized versions of the data for faster access. In a another instance, Twitter found its use of DRb, a mechanism for remote method invocation (RMI), had created a fragile single point of failure. It replaced DRb with Starling, a distributed messaging queue that gave it looser coupling of message producers and consumers, and better fault tolerance. > It is of no small significance that Twitter’s engineers chose to absolve Rails of being at fault for their problems; instead of offloading the blame to an external factor, they chose to take responsibility for their own design decisions. In fact, this was a wise choice. Twitter’s engineers knew that reimplementing the same architecture in a different language would have led to the same result of site outages and site sluggishness. But online rumor mills were abuzz with hints that Twitter was planning to dump Ruby and Rails as a platform. Twitter’s cofounder, Evan Williams, posted a tweet (shown in Figure 1 ) to assure everyone that Twitter had “no plans to abandon RoR.” It's not that every chapter should open up with a jaunty Malcolm Gladwell-seque tale about the life of loves of professional development. But some of your assertions could be made more compelled with some real-world examples: > As a student of computer science and programming, you’ve learned a significant portion of what you need to know as a rookie professional. The most difficult parts perhaps, but far from the “whole enchilada.” There's nothing wrong with that statement. But there's not much to it besides filler that students have been told for their entire college education. You yourself must have a few personal examples of what the first week of work taught you that 4 years of college didn't. And/or, you may remember a few interns who, despite their college pedigree, found themselves to be completely over their heads. Just even a couple of sentences of showing how you came to learn the wisdom you now dispense goes a long way. Anyway, sorry for the extended critique. I am obviously skipping over the part above to how damn hard it can be to find compelling stories :)