2,229 karma · joined August 15, 2016
* I love solving problems.
* I suck at marketing myself.
* I like working on interesting projects.As soon as I reached this line I was like "OK, I'm done!" LOL!
func printSum(a, b string) error {
x := strconv.Atoi(a) or {
return error
}
y := strconv.Atoi(b) or {
return error
}
fmt.Println("result:", x + y)
return nil
}
or something along these lines...How about creating a "Wall of Shame" page and name shaming such companies, until the get the message that they have the financial resources to pay?
Honestly, when I want to compile a Rust project and see all these dependencies getting pulled in to get compiled along with the project, it gives me goosebumps, because I don't know whether these crates are safe and secured or not...
To clarify: identical male and female Eurasian collared doves give birth to young ones that look *exactly* like Sunda collared dove; even their calling is heavier with more bass in their voice; crazy stuff, yet fascinating at the same time!
You should apply that too and your serious customers will become extremely careful after the first shock...trust me! :D
I read and liked them both, but my heart belongs to Bob's writing, especially the C implementation in Crafting Interpreters and how he explains things.
Unfortunately when you evaluate a project, initially everything looks and feel just right, that you wouldn't have any problem delivering the end result as soon as possible.
But..! We know how customers ask for small "favors" of "tiny" changes that won't affect the whole project, or so they think(!), which eventually end up delaying the whole development as they become painful hurdles, only to find yourself struggling to deliver the project so you can get paid in time.
Those who know this nightmare, know!
A developer, programmer, software engineer, call this category of work however you like, it uses the brain at such relentless limits, implicitly or explicitly depending on the problem a person it's currently working on, it takes an incredible amount of effort to relax your mind at the end of the day.
I remember working on a very difficult project for a customer and I would sleep for 4-5 hours per day until I deliver it, and by the end of the project I was so exhausted that I had to take a whole week to cool down my brain and relax my body.
It took me a whole month to fully recover!
I have worked as a construction worker with my father and I know how to grow my own fruits and veggies; I know the struggles with those things...but trust me, you cannot compare the two by any means!
Using your body exclusively it can be tiring indeed, but at the end of the day, you will have a nice shower, eat and rest well, and the next day you will be good to go; whereas with using your mind exclusively can be so dangerous in so many ways!
At least, that's my case.
I am certain that whenever the opportunity arises to change my professional direction, I will do it immediately.
To me personally, as a profession, technology is not worth it anymore; it has lost its meaning.
I just use it as my leisure, nothing more.
I wonder why...
I use Vim, not neovim, and I use coc.nvim; it supports LSP servers just fine, I'm quite pleased!
https://www.reddit.com/r/nostalgia/comments/xbehqk/2000s_int...
1. Good design is innovative
2. Good design makes a product useful
3. Good design is aesthetic
4. Good design makes a product understandable
5. Good design is unobtrusive
6. Good design is honest
7. Good design is long-lasting
8. Good design is thorough down to the last detail
9. Good design is environmentally-friendly
10. Good design is as little design as possible