Viewing profile — dpenguin
dpenguin
HN member- Joined
- Wed, Jun 03, 2020, 7:24 PM UTC
- HN karma
- 44
- Public activity
- 40 items
- HN profile
- View on Hacker News ↗
About dpenguin
No profile information was provided.
Recent public activity
-
comment
Comment #23559991
There are a lot of arguments about how DoH with TLS 1.3 will give us privacy etc by the proponents of DoH(not this article).. but it’s basically moving the trust from ISPs to CDNs.…
-
comment
Comment #23521541
It was not a counter argument to anything per se. Just pointing out that even with episodes of failed estimates, there is reason to continue estimating.
-
comment
Comment #23521196
Just woke up. Totally agree with this article, even though it was published 4 hours ago in the early hours of the morning!
-
comment
Comment #23512028
Got it. Better to stick to tried and tested “boring” stuff and actually code small functionality yourself than chasing a thousand line library for trivial stuff. At work, someone u…
-
story
Ask HN: DevOps folks, how much time do you spend on security vs. compliance?
I keep hearing from some DevOps leaders that compliance is a pain in the behind and they spend an inordinate amount of time on compliance certifications. Would like to hear more vi…
-
comment
Comment #23511125
Would you say SpaceX launch is novel? Did they do it on schedule? Software is not rocket science. Rocket science is not rocket science.
-
comment
Comment #23511105
That’s cheating. No, that’s not what happened in that org though.
-
comment
Comment #23511084
Yeah. The reason I mentioned it is to highlight that the business often needs to know what something will roughly cost and cannot just headfirst five into it. Estimation is a form …
-
comment
Comment #23507475
Looks like tech debt to me. It’s understandably a big project. But you can still start breaking it down, correct? Break it down by services first. Then do estimates for say 2 servi…
-
comment
Comment #23507434
Ah! xml.js
- comment
-
comment
Comment #23507383
Code organization (part of Architecture) matters a lot here. Especially in large code bases. Software is meant to be “soft” or pliable easily. To do that, one should be able to alt…
-
comment
Comment #23507356
Let me clarify: when I said “they are not qualified for the job” I meant they are not qualified to produce the estimate yet. They can always go back and learn what’s needed and com…
-
comment
Comment #23507326
It could be because you are working on a brand new area every single “Sprint “(or equivalent). That’s not prudent assignment of resources(the manager should know this). I have work…
-
comment
Comment #23507170
It only means you didn’t do your homework(no offense, everyone falls into this trap too and conclude the issue is that estimation itself is not possible ). You can’t give an estima…
- comment
-
comment
Comment #23506899
How often do you really do novel/unique/innovative stuff? Honestly.
-
comment
Comment #23506679
99% of teams that need estimations are not in a phase where they are designing something that is hard to estimate. And those that are usually are prudent enough to not bother R&D w…
-
comment
Comment #23486124
Potentially somewhat controversial take on this: why do college grads deserve a better job than, say, high school grads if the subject they studied in college is not particularly r…
-
comment
Comment #23474188
It’s basically modified Parkinson’s law at play - work will expand to most available workforce. With increased automation, either new jobs are created(thereby increasing the overal…
-
comment
Comment #23473017
Exactly what I was thinking as I was browsing this thread. If I can understand the code by visiting as few files as possible and reading as few lines as possible and not having wor…
-
comment
Comment #23463861
Cool! You could provide a read line-based command line interface with server or client driven completions to make it even more ready to use.
-
comment
Comment #23462122
Agree with another who said it’s always the people that end up being a problem and not tech. Unfortunately a lot of tech geared towards fixing the problem ends up creating more of …
-
comment
Comment #23461084
Sorry “typo”. I meant, as easy to use as Heroku is.
-
comment
Comment #23460976
Can fully relate to the author. We have been struggling with effective k8s at our company for 2 years now. Too much to learn to get your first service in production. You will end u…