catwind7

6 ms·

1.
by catwind7 4y ago
formalized expression is detail and while that detail may not be complex for a programmer it can be completely meaningless to a user. I agree with you in part but i think worth recognizing that if we all had this attitude then we wouldn&#x2
2.
by catwind7 4y ago
This line stood out to me: > “As it stands now, there seems to be a tradeoff between ease-of-use and control, and until someone figures out how to remove that tradeoff, there will always be a need for engineers who can fully manipulate
3.
by catwind7 4y ago
wow, this is scary
4.
by catwind7 5y ago
i better not tell employers that I haven't touched a physics text book in the last 10 years
5.
by catwind7 5y ago
I really like how she connects the necessity of the software for customers to release risk management. It's a very user-centric view which I like. Helps me understand release processes I've experienced much better from a business
6.
by catwind7 5y ago
what if you have plenty of ideas but you run out of money because you can't ship fast enough? :D sorry couldn't help it on more serious note - I'm curious what you mean by run out of ideas. do you mean product literally not h
7.
by catwind7 5y ago
this convo has made me realize that our terms for testing do not pair well with actual testing practices, which i find easier to conceptualize in terms of "coarseness" relative to fundamental units of work in a system as opposed t
8.
by catwind7 5y ago
by claiming when something stops being a unit test, you have to define what a unit test is. Now, I do think there is a good, reasonable definition of a unit test and it's looser than yours. A single function that reaches out for an API
9.
by catwind7 5y ago
what does unit testing have to do with whether or not you instrument the test with fake responses? those points of contact that you're mocking out at the perimeter, that data will sometimes need to reach a particular function through a
10.
by catwind7 5y ago
I agree with the first part of what you said, but I don't think plain listening is a "new paradigm", albeit I'll grant that it's probably a skill that can be improved. to circle back to the original topic of underst
11.
by catwind7 5y ago
it really sucks and I feel it's gotten worse with zoom. Sitting in retro meetings in the past year I've definitely noticed an uptick in people just talking and not actually responding to what someone just said. very frustrating.
12.
by catwind7 5y ago
> One may argue that a motivated and smart student can overcome such obstacles and get her foot in the door by attending such schools. But then the challenge is flipped: not many such students need to attend such schools. i guess it que
13.
by catwind7 5y ago
what I've seen a lot over the years is that an engineer gets asked about timeline, thinks for about 10 seconds, blurts something out, then if it's off (too short) they bust their asses / cut corners trying to hit their own es
14.
by catwind7 5y ago
it seems to come from the same place of wanting a simple rule to pattern match against some problem space so we don't have to think too hard about it every time. also ... the author cites sam altman as evidence that his thinking is on
15.
by catwind7 5y ago
I can relate to a lot of this. One thing I learned about myself recently is that I tend to default to programming because it practically guarantees that I'll feel good (dopamine from making things work, fixing bugs). Since I don't
16.
by catwind7 5y ago
mixed feelings about this not being the top comment
17.
by catwind7 6y ago
fantastic :)
18.
by catwind7 6y ago
agree with this ^. Pretty sure the book was written with STEM (but really, comp sci) new grads in mind
19.
by catwind7 6y ago
agree with the adaptability of change requests from clients, but i would say only insofar as the design issues you're mentioning are actually addressed as quickly as they are surfaced. Otherwise this type of building eventually grinds
20.
by catwind7 6y ago
this made me chuckle
21.
by catwind7 6y ago
> When tech debt sand gets in the software delivery gears, the allure of vendors increases Well put. Could not have said this better myself. I've experienced situations where the tech debt sand is a consequence of fairly unique busi
22.
by catwind7 6y ago
Looks great! :thumbsup:
23.
by catwind7 6y ago
different companies need different skills and it changes even as a company grows. Part of the frustration about this entire process is that it feels very cookie cutter and sort of like a lowest-common-denominator type effort on behalf of co
24.
by catwind7 6y ago
Most places will also probably have you spending a good chunk of time maintaining legacy code rather than inventing entirely new business units / products / platforms. I can't imagine what the maintenance burden is like at hu
25.
by catwind7 6y ago
I see - just curious, in what way is it mostly misused and can you be specific about how I've misuse it? I'm still not convinced I've misused it but would like to know so I don't do it again
26.
by catwind7 6y ago
> The problem is they've kept making it worse and worse to unanimous dissent Where's your data on "unanimous dissent"? Also, there's often a silent majority of your products where people are totally happy with it
27.
by catwind7 6y ago
This is a great answer - and this doesn't just affect products with hundreds of millions of users. It's a classic case of Innovators Dilemma ( https://en.wikipedia.org/wiki/The_Innovator%27s_Dilemma ).
28.
by catwind7 6y ago
https://formium.io/ is the company behind react's popular formik library
29.
by catwind7 6y ago
Not at all - I still favor vanillajs if only to avoid the bloat of the whole modern js toolchain (webpack...babel...extra compile times) There's also a big difference for us within the form world between forms with ephemeral state and
30.
by catwind7 6y ago
I still have reservations about moving too heavily towards an SPA - we still mostly have server-side rendered pages that render with react components so we don't have to deal with things like client side routing. It's also still i

More ›