{"id":700,"date":"2014-07-06T02:05:56","date_gmt":"2014-07-06T06:05:56","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/acts\/?p=700"},"modified":"2019-02-26T16:32:48","modified_gmt":"2019-02-26T21:32:48","slug":"peoplesoft-and-star-trek","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/acts\/2014\/07\/06\/peoplesoft-and-star-trek\/","title":{"rendered":"PeopleSoft and Star Trek"},"content":{"rendered":"<p>When I first encountered peoplesoft, I was woefully underwhelmed. Like something a newbie PHP person would have written 10 years prior. In fact, I&#8217;ve worked with dozens of similarly functioning sites over the years, so it honestly wasn&#8217;t a big deal.<\/p>\n<p>I think I first noticed it was a big deal when I got an email about a year ago from HR, saying they&#8217;d give bonuses to people who referred Java and PeopleSoft professionals. That got me to thinking PeopleSoft and Java developers were roughly equivalent. I noticed the positions for them were being posted at roughly the same grade. I didn&#8217;t think much of it beyond that.<\/p>\n<p>Recently I figured out what PeopleSoft development actually is. It&#8217;s not coding at all. It&#8217;s configuration management. Not too far removed from someone who can work in Drupal. I was floored. Not because there&#8217;s anything wrong with that, but because such a focus was being put on configuration over custom. I find this both refreshing and scary.<\/p>\n<p><a href=\"http:\/\/blogs.law.harvard.edu\/acts\/files\/2014\/07\/WilWheaton.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-702\" src=\"http:\/\/blogs.law.harvard.edu\/acts\/files\/2014\/07\/WilWheaton.jpg\" alt=\"WilWheaton\" width=\"600\" height=\"458\" srcset=\"https:\/\/archive.blogs.harvard.edu\/acts\/files\/2014\/07\/WilWheaton.jpg 600w, https:\/\/archive.blogs.harvard.edu\/acts\/files\/2014\/07\/WilWheaton-300x229.jpg 300w\" sizes=\"auto, (max-width: 600px) 100vw, 600px\" \/><\/a>I woke up the other night and couldn&#8217;t get back to sleep thinking about this. Was this the future of web development? Configuration management? Was web development eventually going to become 90% &#8220;PeopleSoft&#8221;? I&#8217;ve even been thinking it made sense because Welsey Crusher &#8212; while gifted &#8212; was not the kind of person I saw coding the woman\u00a0in red in C. That would require a team of developers. Sure, maybe there&#8217;s some awesome libs in the future, but more likely programming in the future will be tantamount to drag and drop. I mean, think about how they controlled the Holodeck, they were giving basic commands, parameters and values. Voice activated PeopleSoft.<\/p>\n<p>Eventually hardware will get better and better, and the bloat of PeopleSoft and like platforms will be less of an inhibitor.<\/p>\n<p>Eventually is a ways away though. Today, speed is paramount. Users demand immediate gratification, and that requires optimization. And PeopleSoft can&#8217;t meet user expectations in that way. So it just remains a corporate institution. Something people will put up with because that&#8217;s what&#8217;s been sold to them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first encountered peoplesoft, I was woefully underwhelmed. Like something a newbie PHP person would have written 10 years prior. In fact, I&#8217;ve worked with dozens of similarly functioning sites over the years, so it honestly wasn&#8217;t a big deal. I think I first noticed it was a big deal when I got an [&hellip;]<\/p>\n","protected":false},"author":4571,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[111262,1389,259,111259,111260,625],"class_list":["post-700","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-configuration-management","tag-future","tag-innovation","tag-optimization","tag-peoplesoft","tag-star-trek"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/700","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/users\/4571"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/comments?post=700"}],"version-history":[{"count":2,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/700\/revisions"}],"predecessor-version":[{"id":703,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/700\/revisions\/703"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/media?parent=700"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/categories?post=700"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/tags?post=700"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}