1
point
elyseum
Joined 198 karma
- elyseumI support your statement for custom dev applications. Unfortunately some large enterprise applications like D365 still require the Framework :(.
- Anybody who can suggest a readable (non-expert) non-fiction book on dinosaurs?
- I always found it ironic that a book that advocates concise documentation and diagrams over text looses itself in way too much narrative.
- Yes. It applies to what you do / make. You can’t copy (parts of) the written text, but you can act (write your own interpretation) with the ideas in that text.
“Copyright is intended to protect the original expression of an idea in the form of a creative work, but not the idea itself.”
- So you liked Feedly for almost 10 years, but never bothered to support them financially. And now you complain that they go the extra mile trying to earn money?
- Setting that up was not part of the 20% effort that delivers 80% of the value ;).
- Posted here 6 days ago: https://www.hackerneue.com/item?id=28050750
- Interesting promise. Will give it a try. Does anybody known similar tools, written in a different language (no expertise on Go)?
- Somebody took the Make A Lisp challenge (https://github.com/kanaka/mal) quite serious :D
- Maybe not a starting point because it’s too advanced, but Make A Lisp has example implementations for +80 languages now: https://github.com/kanaka/mal
- No need to ‘return’ when you throw an error, but your approach is valid IMO: if structure / readability is that important, refactor the switch to it’s own method with only if checks in it. Hard to make that simpler and more readable.
- A good example of: just because you can, it doesn’t mean you should. Yes, the if/else sequence is a bit more unstructured in terms of code layout, but chances the next developer browsing the code will instantly know what it does will be much higher.
- Slack down, productivity up!
- For those who don’t know the original series (Lisp is not part of it as far as I can tell): https://en.m.wikipedia.org/wiki/The_Manga_Guides Nice to read and collect.
- I see some criticism in this thread towards DEV, but 6 day working weeks... to me it’s a classic example of incompetent managers trying to fix a project they lost control of. I mean, you work with highly skilled people, thrilled to be part of the next big thing and all you can think of is bringing in the whip. As if people aren’t motivated enough and not doing overtime already, giving the best they can to make it work.
Yes, it’s the DEVs that write the bugs, but it’s hard to not get sloppy from time to time when there’s constant pressure to make progress and meet deadlines for the sake of meeting them. It’s not DEV’s fault the intermediate deadlines apparently were just green coloured cells on an Excel sheet and did not include actual quality checks, or planning / priority reviews to prevent quality issues and excessive overtime.
- True. Learning tools doesn’t have to be a negative thing.
- To me, it’s about being able to bring (direct) added value to a company. Focussing on specific tooling is an example of doing that. Learning deeply is important as well, but it usually brings value to the company on the long term (if at all).