0db532a0

21 ms·

1. 181.▲
   by 0db532a0 8y ago

   I’ve always wondered what the black bits in my steel cut porridge oats are.
2. 182.▲
   by 0db532a0 8y ago

   Interesting. Got a source on that?
3. 183.▲
   by 0db532a0 8y ago

   That is interesting. What made you stay away from returning an error if someone tries to post without a receiver?
4. 184.▲
   by 0db532a0 8y ago

   Would there be no way for the server to indicate over HTTP to curl that it is not ready to receive until the receiver has connected? Then curl might be able to wait until it reads from the pipe.
5. 185.▲
   by 0db532a0 8y ago

   I did 150mph on the Autobahn last year on my motorbike on a straight stretch with three lanes. I thought I’d play it safe and stay in the outside lane in case someone from the inside lane decided to overtake another. Two cars undertook me,
6. 186.▲
   by 0db532a0 8y ago

   You’ve moved the OS into the docker image, so it’s basically the same OS, therefore I’m satisfied. What runs the docker image is less important, but it would be better to have uniform computers and OS in case one of them breaks. You can rep
7. 187.▲
   by 0db532a0 8y ago

   I agree that CI is a brilliant investment. Also it can initially be as simple as a git hook. However, I agree with the author’s point that you do not need a Kubernetes distributed NoSQL megagalaxy when you have a number of customers which y
8. 188.▲
   by 0db532a0 8y ago

   There should be a process in place for routine testing on each target environment. Testing on BeOS shouldn't just be done because Bob happens to like doing his development on BeOS.
9. 189.▲
   by 0db532a0 8y ago

   You're right on that. I never viewed backend and frontend as the same team. Obviously they should be using the appropriate tools for their job.
10. 190.▲
    by 0db532a0 8y ago

    Relevant reading: The GNU coreutils manual https://www.gnu.org/software/coreutils/manual/html_node/inde...
11. 191.▲
    by 0db532a0 8y ago

    You might find this interesting: The Ego and its Own, by Max Stirner https://en.wikipedia.org/wiki/The_Ego_and_Its_Own
12. 192.▲
    by 0db532a0 8y ago

    Setting the git diff algorithm to patience or histogram would probably solve a lot of the merge issues. You’re right on the web views. It would be nice if they respected the algorithm setting from the git config.
13. 193.▲
    by 0db532a0 8y ago

    Thanks for the input. Couldn’t that be solved by automated building and testing over multiple VMs?
14. 194.▲
    by 0db532a0 8y ago

    How did it bite you in the ass out of honest interest? I have not done commercial C++, so I would be interested to know.
15. 195.▲
    by 0db532a0 8y ago

    git diff -C can show rearrangements and renames.
16. 196.▲
    by 0db532a0 8y ago

    I respect your preference. I now prefer the tranquility of assimilation and consistency in my career. I would also tell recruiters that I do not care about OS and platform choices, as long as they are uniform across unique teams.
17. 197.▲
    by 0db532a0 8y ago

    Multiple build targets enforced uniformly over the whole team.
18. 198.▲
    by 0db532a0 8y ago

    Docker, Vagrant, build tools are all the same. They should just be uniform. Don't hire someone unexperienced in the uniform language. After that, one-time investment in assimilation to the uniform environment. That versus never-ending
19. 199.▲
    by 0db532a0 8y ago

    That's it, isn't it? I cannot think of any other profession where such a large majority of people defend so strongly their right to work on their own terms inside an organisation. When was the last time you heard about a solicitor
20. 200.▲
    by 0db532a0 8y ago

    If there aren't easily available and widely used tools for a chosen language, then it might not be the right choice.
21. 201.▲
    by 0db532a0 8y ago

    I don't know what led to the decision. The CEO had already built a very successful company on the same principles. The company where I worked had these same principles from day one. This also happened to be a start-up and not a megacor
22. 202.▲
    by 0db532a0 8y ago

    Developers are not unique in thinking that they are unique.
23. 203.▲
    by 0db532a0 8y ago

    Wikipedia does not say that the above is an example of the passive voice. Passive voice requires past participle. "is" above is present continuous anyway. I don't think that running a software team like a paramilitary group i
24. 204.▲
    by 0db532a0 8y ago

    I don’t agree with the analogy. The interface of a drill is much less complex and is basically the same over all brands. The longevity and power may well differ. Drill bits are standard and work as well in a Makita as in a DeWalt. I don’t t
25. 205.▲
    by 0db532a0 8y ago

    There’s a reason behind uniform in many institutions.
26. 206.▲
    by 0db532a0 8y ago

    Yes. I hated it in the beginning, but it was so nice later on to be able to work together, share tools, share build scripts, to know my stuff would work on their stuff and to concentrate on the real issues.
27. 207.▲
    by 0db532a0 8y ago

    I have used Emacs for over half my life. I had to use IntelliJ. Coding style was enforced. Same OS. It was fine. Maybe a bit of a struggle in the beginning. It was actually brilliant. I was soon whizzing away having learnt all the new short
28. 208.▲
    by 0db532a0 8y ago

    See “team”.
29. 209.▲
    by 0db532a0 8y ago

    You underestimate the value of uniformity and group pressure. Everyone gets used to the one environment in the end. How did you pick up a programming language and editor in the first place? How did you pick up a new one? It was fine. If peo
30. 210.▲
    by 0db532a0 8y ago

    I agree with you, but I am not the manager.