larve

39 ms·

1. 421.▲
   “Autistic people can’t acknowledge when they’re wrong”(the.scapegoat.dev)

   249 points by larve 4y ago|496 comments
2. 422.▲
   Barbara Liskov, the Architect of Modern Algorithms(quantamagazine.org)

   39 points by larve 4y ago|8 comments
3. 423.▲
   by larve 4y ago

   I combine both freely. I have a "wiki" part that's mostly starting pages for individual topics, a structure notes part that are a cross between a draft article and an index page. They're concepts I'm trying to work
4. 424.▲
   by larve 4y ago

   Digital notes are much more useful for getting long term value out of them, I found. Paper notes are fun, and it's much easier to sketch things freely and just doodle on them. Paper sketchbooks are also really useful as temporal artifa
5. 425.▲
   by larve 4y ago

   I have been keeping sketchbooks since 2010, where I decided "this is something I'm going to do forever". I have started another "I'm doing this forever"-project where I started writing daily in 2020, my obsidia
6. 426.▲
   Writing made me a better engineer(the.scapegoat.dev)

   2 points by larve 4y ago|0 comments
7. 427.▲
   How I learned strategic thinking as an engineer(the.scapegoat.dev)

   2 points by larve 4y ago|0 comments
8. 428.▲
   by larve 4y ago

   for sure. but it's not "hard" (of course abstraction is hard to learn and see, but not to implement, I hope you understand my meaning here. I apologize for the lack of clarity) to build something like (very rough sketch):
9. 429.▲
   by larve 4y ago

   Thanks for the comment! As a counterpoint, I used PHP5 when writing https://www.goldeneaglecoin.com/ and it was always < 50 ms on my endpoints, running on some crusty hosted celeron at the time. Adding caching and opcach
10. 430.▲
    by larve 4y ago

    I definitely studied that book when it came out. I feel my definition is the same as his "Legacy code is simply code you got from someone else". I have seen MANY legacy codebases with tests. Surprisingly often these tests are not
11. 431.▲
    by larve 4y ago

    That's actually not my experience. I pretty much always had complete technical freedom when brought in as a freelance on e-commerce PHP applications. As long as it enables the business, they let the nerd do the gobbledigook.
12. 432.▲
    by larve 4y ago

    I feel this is more a "classic" ORM problem. Wordpress is absolutely egregious here as well. I wrote up my strategy in another post, but I usually develop using the ORM (often, ORM for writing, SQL builder + ORM for querying, beca
13. 433.▲
    by larve 4y ago

    My approach (very similar than when I write C or raw JS) is to use a few "cleanup" APIs or libs that hide the nasty stuff (string handling / array iteration / SQL building), because I know I don't want to deal with
14. 434.▲
    by larve 4y ago

    I think PHPStorm has been very helpful as an IDE for over a decade. One of the things I do like about PHP is that while most legacy codebases out there are lousy (even when good developers are involved), and often lousy for totally legitima
15. 435.▲
    by larve 4y ago

    I really like the vercel and co approach to the dev cycle. It's as easy as (if not easier) PHP and you get a huge boost of monitoring / infra tools for a minor cost. I think we are seeing a lot of the "yeet and get shit done&
16. 436.▲
    by larve 4y ago

    I think the point is that you can do both. Sometimes being able to yeet a PHP file to some PHP/wordpress hoster and get a project done in an afternoon is exactly what is needed, because even spending 2 or 3 days to set up a proper CI a
17. 437.▲
    by larve 4y ago

    Thanks for the comment! I think the "the more things change, the more they stay the same" is a great thing, and something to very much be aware of and study. The move back and forth from backend state to frontend state to slim app
18. 438.▲
    by larve 4y ago

    It always depends on the situation, but I do value the stateless approach "by default" of PHP because it makes shoddy code / legacy code that has grown through generations of uninterested developers much easier to deal with.
19. 439.▲
    by larve 4y ago

    Yes, nothing comes for free. opcache, object cache + db pooling is something I always turn on. Then, for app performance: My approach is to usually design the app / refactor the app so static content can be fully cached. In ecommerce s
20. 440.▲
    by larve 4y ago

    You can also do some pretty "fun" things with PHP leveraging the opcache. I wrote what in my own personal biased benchmark was the fastest mustache template renderer by transpiling mustache to php files and then "compiling&qu
21. 441.▲
    by larve 4y ago

    Thanks for the thoughtful comment. I indeed haven't fully articulated what is driving me to write this piece (besides a desire to give PHP a bit of love as it is so harshly criticized for reasons I don't entirely understand). I fi
22. 442.▲
    by larve 4y ago

    Thanks for commenting! I always have a hard time understanding what exactly is meant with comments like these. We can all agree that PHP has a wildly uneven standard library, had its fair share of security-relevant footguns, tends to have u
23. 443.▲
    by larve 4y ago

    I assume this is meant in snark, but jquery was such a breath of fresh air when it came out. I have been doing some SPA stuff with raw DOM, later on mootools and yahoo ui around 2003-2004, and that was really the wild west.
24. 444.▲
    by larve 4y ago

    thanks for reading! I use legacy code as in "code that was written yesterday or earlier", or in a less jokey fashion as "code that noone really feels ownership for", usually a codebase that shows the sign of many develop
25. 445.▲
    by larve 4y ago

    I think Java and C# are indeed my favorite languages for huge projects with wildly varying developer competence. Python is probably my most hated for that situation.
26. 446.▲
    by larve 4y ago

    I think I learned it through a couple of venues. I am still thinking this one out, and definitely plan to write a post about it. 1. designing "big" enterprise software from scratch, on paper, and then building a toy implementation
27. 447.▲
    by larve 4y ago

    thanks for reading and commenting. I am incredibly bullish on static typing and static analysis in general. There are quite a few tools that bring these to PHP and JS (I am not entirely happy with PHPStan / Psalm, I am very pleased by
28. 448.▲
    by larve 4y ago

    Author here, thank you for reading the article and taking the time to comment. Every legacy codebase I have worked with was actually a successful business. That probably plays a big role in why I enjoy working with them. The job is not easy
29. 449.▲
    I still love PHP and JavaScript(the.scapegoat.dev)

    427 points by larve 4y ago|393 comments
30. 450.▲
    Data Organization in Spreadsheets (2017)(tandfonline.com)

    1 points by larve 4y ago|0 comments