edw519 · HackerTrans

vor 3 Jahrendiscuss

UNIX too

vor 3 Jahrendiscuss

Thanks, aredirect!

My next phase is to put the PICK-generated svg into codepen and provide links to show how to draw the art with code.

edw519

vor 3 Jahrendiscuss

I used my work email and then forwarded it to my g mail.

If you have concerns about doing that, you can just download it from my website at

http://eddiots.com/UVTE_WINDOWS_11.4.1.zip (You may have to cut and paste this link into a new tab. HN doesn't seem to like this.)

If you have any problems or need the UNIX version, just reply here or contact me. email on my profile. Let me know how it goes.

edw519

vor 3 Jahrendiscuss

Thanks, Mister_Snuggles, for reminding me I'm not the only one left.

I HAVE to code in PICK.

"Unless it comes out of your soul like a rocket, unless being still would drive you to madness or suicide or murder, don’t do it." - Charles Burkowski

(Funny, they named the current support company "Rocket".)

Here's the link to the current Universe trial version (free and good until 04/2025. Get it, install it, and make something with it. Please don't let that part of you die.

https://www.rocketsoftware.com/products/rocket-multivalue-ap...

edw519

vor 3 Jahrendiscuss

https://en.wikipedia.org/wiki/Pick_operating_system

This has accounted for about 90% of everything I've built since 1985.

Pick code generates my side project: https://eddiots.com/1

edw519

vor 10 Jahrendiscuss

It usually comes in a phrase similar to "I know how to program, but I don't know what to program."

"How" is about yourself. "What" is about others. Both are important, but "How" ususally comes first. The best way to transition from "How" to "What" is to trust that you have enough "How" (you probably do) and talk to enough others to understand their "What". That oughta give you plenty to do.

In the software community the rule is "don't reinvent the wheel." It's almost frowned upon if you rewrite a library when a mature and stable option exists. While it is a good rule in general, novices should not be afraid to reinvent the wheel. When it is done for learning or practice, it's totally OK to make a wheel!

Yes! The best thing I've ever done to get better ("graduating" to the next level) was to rewrite something else. Sometimes because I thought it sucked, sometimes because it was so cool that I wanted to grok how it worked from the inside out, but never because it needed rewriting. I have never learned anything reading someone else's code. I have always learned tons rewriting it.

Don't get the notion that you need to have the best idea ever before you write a program either.

I never write anything in order to get ideas. I write stuff in order to fill my tool box with enough skills and wisdom so that when I do get an idea, I'll be able to run with it.

How many of you have been in the situation where you think "I don't know what to program?" How did you handle it? What advice would you give to others in that situation?

Just write something, anything. You probably won't know where this will take you, but rest assured, it will take you somewhere you never would have found by not writing it.

Great post! Thank you, OP.

edw519

vor 11 Jahrendiscuss

Technology

  1. Know your apps.
  2. Understand your domain.
  3. Understand your technology under the hood.
  4. Have an idea of how you'd approach each project.
  5. Write detailed technical specs for juniors.
  6. Write general technical specs for seniors.

People

   1. Be nice.
   2. Understand you are a resource provider, not a boss.
   3. Get shit done.
   4. Ditch team building gimmicks (see #3 for what's important).
   5. Listen!
   6. Share. Share. Share. 
   7. Teach. Teach. Teach.
   8. When you need a bad guy/gal, you're it.
   9. When you need a good guy/gal, your people are it. 
  10. Know how to run a project as needed.
  11. Know how to run a meeting as needed.
  12. Don't be bashful.
  13. Don't be (too) stubborn.
  14. Stand your ground with users/bosses.
  15. Have fun & foster an environment for others to too.
  16. Always do the right thing.
  17. Never stop being a programmer.
  18. Never stop loving building stuff.

comments