Naming things is one of the hardest things a programmer needs to do. 
Seriously.
On Tuesday, March 8, 2022 at 6:08:09 AM UTC+7 ba...@iitbombay.org wrote:

> GoBOL, anyone?
>
> > On Mar 7, 2022, at 2:20 PM, Rob Pike <r...@golang.org> wrote:
> > 
> > It could have been
> > 
> > interface 
> UnreceivedMasterOrdersInterfaceThatCanBeUsedToCallGetUnreceivedByProductsWarehouseAndCompany
> > 
> > Seriously, though, your example isn't even on the same planet as some
> > of the examples I've seen. (Neither is my parody.)
> > 
> > Sympathies.
> > 
> > -rob
> > 
> > On Tue, Mar 8, 2022 at 7:49 AM Rudolf Martincsek <rud...@gmail.com> 
> wrote:
> >> 
> >> Latest interface my colleagues wrote (it's PHP)
> >> ---
> >> interface UnreceivedMasterOrdersInterface
> >> {
> >> public function getUnreceivedByProductsWarehouseAndCompany(array 
> $productIds, int $warehouseId, int $companyId): array;
> >> }
> >> ---
> >> There is interest to switch to Go for some of the stuff we write, but I 
> decided to leave before that happens. I like programming in Go for myself, 
> and I don't want to start hating it because of nonsense like this.
> >> 
> >> 
> >> On Wednesday, February 2, 2022 at 8:51:54 AM UTC+2 Amnon wrote:
> >>> 
> >>> Idiomatic naming in Go is one of the hardest things to communicate.
> >>> Everyone seems to bring the idioms from previous languages. Dave 
> Cheney writes about
> >>> "Lengthy bureaucratic names carry a low amount of signal compared to 
> their weight on the page".
> >>> Identifiers are not sentences or stand alone stories. They are the the 
> basic building blocks for our code.
> >>> We have all seen code infected by these names - long names leading to 
> long lines of code,
> >>> and verbose walls of dense text, repetitive and hard to read.
> >>> 
> >>> I always encourage people to read 
> https://go.dev/doc/effective_go#names
> >>> to study the Go standard library, and develop a feel of what Go code 
> should read like.
> >>> 
> >>>> 
> >>>> 
> >> --
> >> You received this message because you are subscribed to the Google 
> Groups "golang-nuts" group.
> >> To unsubscribe from this group and stop receiving emails from it, send 
> an email to golang-nuts...@googlegroups.com.
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/00dec58d-421a-4b86-9c15-6533fc648974n%40googlegroups.com
> .
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "golang-nuts" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to golang-nuts...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/CAOXNBZQ9FvDDusTGkRZdJbUNOMCL%2B8Td2QW_7KYQK45CmEUfxA%40mail.gmail.com
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/314e8fe8-6a14-4474-941a-455c8edab3dbn%40googlegroups.com.

Reply via email to