Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Developer's block

underlap.org

Post reply on HN
Print view View original

101–106 of 106 posts

Re: Developer's block

#101

Post by lilerjee »

ksflrn wrote: post #100
lilerjee wrote: post #79

Good article, thank you! I like extreme cycling, and it helped me solved many problems about development. When I'm riding my bike and listening to music, especially when freely imagining and designing my product in my mind, I am very relax. Many aspects of my products were designed while I was riding. Cycling is a great form of exercise. It not only helps you strengthen your body, enjoy the scenery, relax your mind,…

How can one enjoy the scenery and design stuff in the brain all at once? Seems contradictory to me

Sometimes, I found a beautiful view, then I saw and played, it was time to enjoy. Sometimes, there was no good view, and my brain was excited to design my product, I went to a quiet road which had no or fewer people and cars, no other things to distract or bother you, you just was imaging freely and enjoy the process.

Re: Developer's block

#103

Post by glynnormington »

siva7 wrote: post #84
chrisweekly wrote: post #55

Earlier quoted context omitted.

Your linked post about test harnesses is outstanding; thanks for sharing!

I've skimmed the article and still have no clue what you guys are talking about. Is test harness another word for end to end testing?

Did you see this helpful link: https://littlegreenviper.com/testing-harness-vs-unit/. According to that usage of "test harness", it's not the same as a unit test. It's a way of driving code manually to explore different usages and to recreate certain kinds of bugs. It is used to complement unit tests.

Re: Developer's block

#104

Post by glynnormington »

darth_avocado wrote: post #82
Kovah wrote: post #4

There's so much good advice in this article. My number one point that i learned the hard way during two decades of writing software: take breaks when your body tells you to. It's an absolute killer if you force yourself to work on your projects just because there's stuff on your to do list, new issues on Github, or whatever. Just stop working if you don't feel it.

There’s so much good advice in the article and I think most developers know these intuitively to a certain extent. The problem with it though is that corporate culture tends to ignore these and is very unforgiving in my experience. When you have to deliver everything on time, all the time, you can’t take any of this advice and practically use it. Taking time with learning for example is something you can do only when…

That's hard. My only advice when working in a stifling, corporate environment is to find out what your education budget is and then use it for the kind of learning I was referring to in the article. (If you don't have an education budget, that's one more reason to start planning a job move...)

Re: Developer's block

#105

Post by chrisweekly »

siva7 wrote: post #84
chrisweekly wrote: post #55

Earlier quoted context omitted.

Your linked post about test harnesses is outstanding; thanks for sharing!

I've skimmed the article and still have no clue what you guys are talking about. Is test harness another word for end to end testing?

"Compared to unit tests, a test harness is a [usually] simple standalone application that incorporates the system under test, and presents a user interface. Since it is for testing, it may expose internal metrics and allow the user to access parts of the code that are usually hidden."

^ from https://littlegreenviper.com/testing-harness-vs-unit/

Re: Developer's block

#106

Post by chrisweekly »

ChrisMarshallNY wrote: post #93
siva7 wrote: post #84

Earlier quoted context omitted.

I've skimmed the article and still have no clue what you guys are talking about. Is test harness another word for end to end testing?

Well, I thought I explained it well. Frankly, I'm shocked that folks don't know what test harnesses are. They are one of the oldest constructs in Software Engineering. In the days of old, we often called them "Unit Tests." If you want some concrete examples, here you go: Here's my "Spinner" widget: https://github.com/RiftValleySoftware/RVS_Spinner This is the four test harness apps: https://github.com/RiftValleySoftw…

Great examples, thanks for sharing links to a real project. But I'm confused by your assertion, > "In the days of old, we often called them "Unit Tests."

My understanding is, test harnesses are standalone wrapper apps dedicated to testing, vs more granular unit tests which are traditionally colocated with (eg, files alongside) app src code in a given project. Care to elucidate?

Post reply on HN