Jump to content

User:Charlesreid1

From Wikipedia, the free encyclopedia

Bio

[edit]

I am a chemical engineer.

My website: http://www.charlesreid1.com

Useful template for cleaning up old articles: https://wiki.riteme.site/wiki/Wikipedia:WikiProject_Physics/Quality_Control/Reviewing_Cheatsheet

Useful stars to give out: https://wiki.riteme.site/wiki/Wikipedia:Barnstars

Gadget: https://wiki.riteme.site/wiki/Wikipedia:Twinkle

Articles

[edit]

Ongoing Monterey Bay Work

[edit]

Got caught up in a backlog with the first block, on historic buildings:

skipping to outdoors:

Portal:Monterey Bay Area

Pocket

[edit]
{{Press|subject=article |author=Ryce, Walter |title=Monterey's art scene was misrepresented for years on Wikipedia. Is it any better now?  |org= Monterey County Weekly |url=http://www.montereycountyweekly.com/blogs/arts_culture_blog/monterey-s-art-scene-was-misrepresented-for-years-on-wikipedia/article_2ad0f6b6-2295-11e4-bfa4-0017a43b2370.html |date=August 12, 2014}}

subcategories for historic houses on national register of historic places

[edit]

Category:Houses on the National Register of Historic Places in California:

why not a monterey county subcategory?

done

santa cruz county

[edit]

now do santa cruz county:

done

monterey bay area and san francisco bay area to rival los angeles area

[edit]

maybe not such a good idea:

.......

categoroy intersections

[edit]

category intersections:

WikiMedia Commons Work

[edit]

Category:Panoramics in Monterey County, California https://commons.wikimedia.org/wiki/Category:Panoramics_in_Monterey_County,_California

Looking for panoramics by picking through https://commons.wikimedia.org/wiki/Category:Monterey_County,_California

Articles I Have Written or Significantly Contributed To

[edit]

(Still contributing to all listed)

Monterey Bay

[edit]

June 2022:

List of Articles of Interest

[edit]

Low Hanging Fruit

[edit]

Biographies

[edit]

Requires A Lot More Work

[edit]

Requires A Little More Work

[edit]


Links

[edit]
[edit]

Wikipedia:Reviewing

If you're interested in fluid dynamics, there's plenty to do here: Wikipedia:WikiProject_Physics/Taskforces/Fluid_dynamics (for example, you can click on the "stub" or "start" articles and find one to improve)

The Good Article Nominees page Wikipedia:GAN has an Engineering section

The "Wikipedia: The Missing Manual" O'Reilly book is available at Wikipedia here: Help:Wikipedia:_The_Missing_Manual

The extensive "Welcome to Wikipedia" message that shows up on new users' talk pages (which has lots of useful links) is here: User:Charlesreid1/Wikipedia

Deleting Articles

Changing Articles into Redirects

Wikipedia Articles I Enjoy

[edit]

Graphical_timeline_of_the_Big_Bang

19 Guidelines for Creating Software: from The Cathedral and the Bazaar

  1. Every good work of software starts by scratching a developer's personal itch.
  2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
  3. Plan to throw one away; you will, anyhow.
  4. If you have the right attitude, interesting problems will find you.
  5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
  6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
  7. Release early. Release often. And listen to your customers.
  8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.
  9. Smart data structures and dumb code works a lot better than the other way around.
  10. If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.
  11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
  12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
  13. Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.
  14. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.
  15. When writing gateway software of any kind, take pains to disturb the data stream as little as possible—and never throw away information unless the recipient forces you to!
  16. When your language is nowhere near Turing-complete, syntactic sugar can be your friend.
  17. A security system is only as secure as its secret. Beware of pseudo-secrets.
  18. To solve an interesting problem, start by finding a problem that is interesting to you.
  19. Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.

Engrish

Opening of the Fifth Seal

Interpolation (music)

Axis mundi

Vision quest

Emic and etic

Odin

Iannis Xenakis