HackerTrans
TopNewTrendsCommentsPastAskShowJobs

keyraycheck

no profile record

Submissions

Why the gradient is a list of partial derivatives

blog.michalprzadka.com
7 points·by keyraycheck·hace 2 meses·0 comments

AI and Junk Development

zkmarek.com
3 points·by keyraycheck·hace 3 meses·0 comments

Ask HN: How are you hiring for remote roles in the era of AI?

3 points·by keyraycheck·hace 6 meses·3 comments

The Age of the Super IC

hvpandya.com
3 points·by keyraycheck·hace 10 meses·0 comments

Thinking with Language Models

blog.toasterthoughts.eu
1 points·by keyraycheck·hace 2 años·0 comments

Running a dev shop: Myths and favorable facts

medium.com
2 points·by keyraycheck·hace 4 años·0 comments

comments

keyraycheck
·hace 5 meses·discuss
While number of active users still grows, one have to ask a question, who is left on facebook aside from dopamine junkies and bots.

The only reason why I didn’t delete facebook is messenger, where I chat with old folks.
keyraycheck
·hace 3 años·discuss
It is actually a common practice, if you want to terminate the lease, to stop paying and get evicted. However, they may still be liable to pay for the three or four months they used.
keyraycheck
·hace 3 años·discuss
I would love to know how people work. I wonder what is the alternative.

The board is far from only agile practice and nit obligatory either. Even Epic sounds like an agile term.
keyraycheck
·hace 3 años·discuss
I have a question to non-agile people? How do you work and get things done?
keyraycheck
·hace 3 años·discuss
+1

That is true for deep work like:

- solving mathematical problems

- coding non-trivial stuff

- teaching non-trival stuff

The challange is shallow work e.g.

- replying to emails

- meetings

- scheduling meetings

And than there is no-work:

- checking your phone

- lunch

- walking and chatting before the next meeting

Shallow and no-work can easily eat anywhere between 20 and infinity :)
keyraycheck
·hace 3 años·discuss
+1

I went all the way from Agile maximalist to common sense-ist.

For me agile these days is simply:

- talk to your team to sync often but short

- seek feedback (from stakeholders, ideally users)

- allocate time to work on your backlog so it nice and tidy

and technical stuff:

- release early, release often (i.e. CI/CD/devops stuff)

- automated testing, regular code reviews

- refactoring, working with small commits/PRs

More a common sense, than a "process" or "ideology".
keyraycheck
·hace 4 años·discuss
It is great you had a mentor. I met few people I could learn from and books (including Bob’s) were very helpful. He promoted TDD, good names, short functions etc Is he too dogmatic? Are his function too short? Probably yes.

I never treat his proposals as a silver bullet, but a great source of inspiraton. I wish there were more people teaching those things.
keyraycheck
·hace 4 años·discuss
I think the answer to software apocalipse is both: - get better tools - get better programmers

And in fact we have been doing it - the tools are so much better than they used to be and with tdd, refactoring, patternals and clean code we have been building increasingly complex software with less bugs.

Still a long way to go.
keyraycheck
·hace 4 años·discuss
The world needs many great teachers, and many great builders.

I love taking advice from both groups, treating neither as a silver bullet.
keyraycheck
·hace 4 años·discuss
I generally agree with the article, however it reminds me of what my algorithmic competition mentor once said:

“So you know who java developer is? Someone who doesn’t know Java”.

While the emphasis was not on Java, but knowing a single language.

“If he could learn Java well he could very much learn C++”.

Again emphasise is not on C++ specifically, but any other language really.

Technology landscape changes, stack get more complex.

While we should not expect everyone to know everything all the time, we should expect most developers strive for fullstackness. A ideal perhaps never to be achieved .