vrnvu

15 ms·

1. 121.▲
   by vrnvu 3y ago

   Simple solutions don't get software engineers promoted for their architecture skills, and catchy blog posts can't be written.
2. 122.▲
   by vrnvu 3y ago

   I agree with your point. Nowadays, people seem to be overly sensitive about their code and the way we communicate, among other things. It's important to remember that the code is not a reflection of ourselves, and not everyone will be
3. 123.▲
   by vrnvu 3y ago

   Completely agree with you. I stopped working with Java not because the language or the ecosystem. I stopped working with Java because Java developers and their culture of over-engineering everything defending it as "clean code" an
4. 124.▲
   by vrnvu 4y ago

   Cool tip thanks for sharing! I love letting process crash *when possible* on failures so the OS restart them for me versus trying to handle it manually at process level.
5. 125.▲
   by vrnvu 4y ago

   Can we stop saying that the 'over engineering interview' is a 'system design interview'? Most real life problems don't get solved by adding queues and moving to an event driven architecture with thousands of micro-s
6. 126.▲
   by vrnvu 4y ago

   > TDD is a good tool for enforcing that, as you only get to write code that you have a failing test case for. TDD encourages the use of mocks and unit testing to increase code coverage. And unit testing is specially dangerous. You write
7. 127.▲
   by vrnvu 4y ago

   The problem with the contemporary "clean code" concept is that the narrative that performance and efficiency don't matter has been pushed down the throat of all programmers. Re-usability, OOP concepts or pure functional style
8. 128.▲
   by vrnvu 4y ago

   How does these performance optimizations you mention translate to cost? How much money are you saving monthly for example? It's hard to justify the effort to write fast code nowadays without talking about cost or revenue.
9. 129.▲
   by vrnvu 4y ago

   Great post thanks for sharing. I also highlight this one: http://widgetsandshit.com/teddziuba/2011/12/process.html
10. 130.▲
    by vrnvu 4y ago

    Sorry, does anyone mind to explain/reference what COM is?
11. 131.▲
    by vrnvu 4y ago

    I upvoted it because the paper is simple and easy to follow. It defines some properties of flame graphs and makes us of them to make conclusions about performance regression, A/B testing and how to have better profiling results removin
12. 132.▲
    by vrnvu 4y ago

    You can learn Go in 2 weeks. That's one of it's selling points! Just dig into the official resources [1]. https://go.dev/doc/
13. 133.▲
    by vrnvu 4y ago

    So what the author is suggesting is basically improving cache locality using linear data structures. Use data structures that fits your CPU/GPU. Use algorithms that make good use of your CPU/GPU... Add branch prediction and good m
14. 134.▲
    by vrnvu 4y ago

    Observability is the other side of statistics.
15. 135.▲
    by vrnvu 4y ago

    Really interesting approach. Thanks for sharing. Do you remember by any case where to find any real example? I'm digging into Golang's repositories trying to find one...
16. 136.▲
    by vrnvu 4y ago

    I love Chuck Moore's minimalism applied to programming. [^1][^2] It goes hand in hand with the UNIX philosophy of keeping things simple that we can see in other software (linux) or languages (LISP, Go, Erlang )... Also, I've alway
17. 137.▲
    by vrnvu 4y ago

    Beautiful explanation. After reading this I wonder if anyone knows about homomorphic encryption and ZKP uses for role/policy management? Or something similar? They main uses I know for ZKPs are in open distributed scenarios but I wonde
18. 138.▲
    by vrnvu 4y ago

    I got me a copy of The Unix Programming Environment (1984) by Pike and Kernighan last year. It has plenty of hidden small design gems or anecdotes like this one. For example, why files don't need a \EOF char, it's implicit when yo
19. 139.▲
    by vrnvu 4y ago

    I dislike the example. The author says that because we have a complex function, and the HTTP handler is designed the way it is, we cannot avoid running into problems. I disagree. This are two separate things. You could take a more functiona
20. 140.▲
    by vrnvu 4y ago

    I live in Spain. To clarify. Free means more taxes.
21. 141.▲
    by vrnvu 4y ago

    It's a common discussion with HTTP Status Codes. Application vs Transport layer. HTTP status are a mix of both and it can be misleading. A couple of weeks ago there was an interesting post about this topic here in HN.
22. 142.▲
    by vrnvu 4y ago

    This is has been a popular topic for decades and I feel like most people get two fundamentals always twisted. Syntax and semantics. Syntax != Semantics. Code readability = syntax that make semantics obvious. If a block of code is written in
23. 143.▲
    by vrnvu 4y ago

    Do you have any data or survey to back your statement? Forgive me if I've misunderstood you but are you saying that Golang is mostly used by young programmers? In my experience most Golang developers are highly experienced... Same with
24. 144.▲
    by vrnvu 4y ago

    I've done pet projects in Haskell, Ocaml, Racket, Rust... Now I'm learning Zig... I've worked for years with Java, Python, Javascript/Typescript... Use to work with Z3... Tried plenty of different stuff. After years my
25. 145.▲
    by vrnvu 5y ago

    Cargo cult programming at it's maximum expression. M. Fowler, Uncle Bob, Kent Beck, GoF authors... Any book or post by these people is always brought up as a must read. A must read to understand why you should *not follow cargo cults*
26. 146.▲
    by vrnvu 5y ago

    Over the years the performance has decreased... exponentially. It is pure craziness that indexing a project takes almost a minute or even more. It's full of env bugs and configuration issues that the developer team seems to not care ab
27. 147.▲
    by vrnvu 5y ago

    Has anyone else noticed how data oriented design has became more common in the past years? At least it's my perception. For anyone interested on similar patterns on performance or good memory access practices. I highly recommend this r
28. 148.▲
    by vrnvu 5y ago

    It's ironic what attempted to be "satiric" and a writing on "good tips" back in 2008 has become a list of red flags in 2022.
29. 149.▲
    by vrnvu 5y ago

    The biggest problem for me is that this style of interview focuses on theoretical efficiency. And the discussions about the interview process only cares about "real world engineering" vs "interview questions". We are dis
30. 150.▲
    by vrnvu 5y ago

    Thanks for taking the time to explain all of these cases. While I was reading I noticed some of them being weird but your insight was really helpful.