Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
beny23
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
Top Software Engineering interview tips
(youtube.com)
2 points
by
beny23
5y ago
|
0 comments
92.
▲
GitOps Is a Placebo
(stevesmith.tech)
1 points
by
beny23
5y ago
|
0 comments
93.
▲
The anti-pattern to Agile is NOT waterfall, it’s your sluggishness
(thedigitalbusinessanalyst.co.uk)
3 points
by
beny23
5y ago
|
0 comments
94.
▲
by
beny23
5y ago
> Know what people are asking you to be an expert in I read this as “leave it to the experts and please realise that sometime it’s not you” which is something that is sometimes quite hard for micromanaging delivery leads or business stak
95.
▲
by
beny23
6y ago
> Cryptocurrencies give us the opportunity to create new financial instruments that do not support industries that are destroying the environment. While crytocurrencies’ ridiculous hunger for energy will destroy the environment all on th
96.
▲
by
beny23
6y ago
Speaking from experience, if you have to go back after many years of development, where most of the team that made the original design choices has left and want to make changes without breaking the system and discover that half of the syste
97.
▲
by
beny23
6y ago
Yes that’s what I meant
98.
▲
by
beny23
6y ago
Ok, my bad for “I think” - I should have said: in my 30 year experience I’ve yet had to come across a system were good tests were a hindrance to performance. I’ve had many a time where complex investigations into performance problems were
99.
▲
by
beny23
6y ago
I think that the “we can go quicker by not testing” is a fallacy. If you do TDD right it will make you quicker, not slower in the short term. Not just the long term...
100.
▲
by
beny23
6y ago
I’d argue that getting performance in a coupled unstructured mess (I’m not saying that’s what SO made) is going to be more difficult.
101.
▲
by
beny23
6y ago
It’s always going to be orders of magnitude more difficult/expensive to retrofit testability. I’d argue that they were successful despite their approach not because of it. I actually have a lot of time for their design choices (monolit
102.
▲
by
beny23
6y ago
Oh absolutely, keeping things simple should never be restricted to just production code. Testing code should be simple too. The idea that tests inhibits refactoring I find problematic though. Good tests enable refactoring. If the tests are
103.
▲
by
beny23
6y ago
In my opinion, the idea that you can have well-tested code OR performance is tosh. If you don’t have good testing and do it regularly how can you refactor your application for speed if you’re not going to be sure that you’re going to introd
104.
▲
by
beny23
6y ago
Was it due to an intern?
105.
▲
Fizzbuzz Without If Clauses
(beny23.github.io)
3 points
by
beny23
6y ago
|
1 comments
106.
▲
Exponential exploit: Why AppSec is hard
(beny23.github.io)
3 points
by
beny23
6y ago
|
0 comments
107.
▲
by
beny23
6y ago
It is very easy to write code that “works on my machine” or “works in QA” and then fails when it hits production volumes or a requirement changes to add more users/elements. Then it often becomes prohibitively expensive to just throw m
108.
▲
by
beny23
6y ago
I’d be a bit sceptical about JSON everywhere as it would mean throwing out all the shell tools and everything having to parse JSON which seems overkill.
109.
▲
by
beny23
6y ago
I think the clarity and brevity of this is amazing. Should be mandatory reading for teaching to people starting in computing. I’ve always thought that the concept of piping input to output and the shell is on of the most powerful “programmi
110.
▲
by
beny23
6y ago
I think the general idea of finding people who take pride in a job well done is a sound one and does often mean the difference between success and failure of a project/business. Where the article completely falls down in is how to meas
111.
▲
More Secure in the Public Cloud
(defencedigital.blog.gov.uk)
4 points
by
beny23
6y ago
|
0 comments
112.
▲
by
beny23
6y ago
I have an intuition that COBOL will become very valuable in the years to come as the majority of greybeards that keep it running will stop work - and then the projects to rewrite core business functions in banks, insurances will come think
113.
▲
by
beny23
6y ago
How many retail banks, insurances and government departments have still got a mainframe sitting at the very back though, based on a good few engagements in banks and gov in the UK, I haven’t yet come across where ultimately some mainframe b
114.
▲
by
beny23
6y ago
There’s also https://github.com/openmainframeproject/cobol-programming-co... which IIRC is an IBM backed open source course.
115.
▲
by
beny23
6y ago
Experience has taught me no longer to be surprised when finding code that determines the number of items in a list by making a SELECT * call to the database and calling .size() on the resulting list and doing it inside a doubly nested loop.
116.
▲
by
beny23
6y ago
Of course with the ubiquity of cloud and minimal images I think the likelihood of having any but the basic tooling on a remote instance is getting more prevalent than not less and the ability to diagnose/debug issues is getting more im
117.
▲
by
beny23
6y ago
The ability to efficiently navigate and edit files while SSH’d into an instance is a very useful skill. You just wouldn’t have the permissions to install your favourite editor and vi is almost everywhere. I had to learn vi when working on g
118.
▲
by
beny23
6y ago
I think > Product teams that opt-out or don’t have their application ready for SRE run on their own. They have full access to the resources they need. The interface with the SRE team is minimal in these cases. and > Custom features lo
119.
▲
Show HN: Eat Out to Help Out Restaurant Finder
(beny23.github.io)
1 points
by
beny23
6y ago
|
0 comments