A New Breed of Confident, Calm Software Engineers Another day in the life of a Software Engineer… Get hired… Get a project, clarify specs, work on it, deliver it, support it… then rinse & repeat. Not bothered by obstacles… Not bothered to learn new things… Not bothered by “cool” projects that others are getting… Not bothered seeing others are getting “cool” titles… Not bothered by layoffs… (try not to “look” like one, at least) Just sit tight, be cool, deliver awesome-ness, when asked or needed. Communicate well with all positive intent. That is it. If you are not groomed as well as the others who got “cool” titles & “cool” projects, then you have all the right to think & say, “not my problem”. Maturity kicks in, along the many yrs of crafting our work. It does, someday, even if you don’t have it today. Enjoy Software Engineering. Bring coolness & awesomeness in the workplace. Relax, do more by doing less. Be happy, be contented. :) Write cool code, by yourself or with the team. Ha ha. O, and cure the World(on the side) when the chance/destiny calls for it!!
Gerardo R.’s Post
More Relevant Posts
-
It is better to be dumb, this kind of mode or setting. :) Because this way, you are free of rigidity, thus creativity can kick at a higher notch. And you can hire creative staff because of free from “genius” expectations allowing higher quality thoughts to occur. And you can cause higher work quality from teammates because of freedom from rigidity. Higher quality interactions, friendship & higher quality creative output. Being dumb is the new in thing. “Genius” is out(very rigid & can cause stereotyping). All the while, IT screening is wrong. ;)
To view or add a comment, sign in
-
Vertically & Horizontally Scaleable Objects Store V2 Beta 2.1 Release! Release link in Github: https://lnkd.in/gNce487g Few things were done/added on this release: * Added support for "store" level cache duration, e.g. - specify no expiration in Redis caching for your end-client's favorite data store. Or specify a data store that uses "sliding time"(TTL) for another favorite data store, and for the rest, 'just specify absolute expiration, e.g. - of 7hrs, so caching can scale! Scaled persisted data virtualization is what is happening. * UUID "to string" function is now using google's uuid.String() function to be RFC.. compliant on UUID string format. * Cleaner code due to refactors. * Added SOP in AWS S3 support, see "in_red_cs3" package. The SOP in File System(FS) (see "in_red_cfs" pkg) is the leanest and most scaleable due to the efficient file I/O & built-in/user definable "data partitioning” across storage drives/sub-system. Both vertical & horizontal data partitioning are supported via an easy lambda expression override. Having these choices either: FS, Cassandra or AWS S3 as "blobs" storage is very convenient, arming IT shops w/ necessary flexibility to choose based on availability, cost & req’d DevOps skills. Link to my previous flex on SOP for more details: https://lnkd.in/gvSYtzwW
To view or add a comment, sign in
-
We now have a real data platform, I invite developers & IT shops to check it out & build on top of it. A modern data platform. It can be leveraged to add SQL, Relational features & support current RDBMS solutions. (if needed or has req’t, but totally not otherwise, because Objects is the direction anyways). As tables are also Objects. :) You can’t solve Objects & horizontal scale in current approaches. Because of “master & slave” rigidity. Orchestration should be done as how SOP does it. Communication less, fully parallel as can be.
Horizontally Scaleable Object Store V2 beta 2 is now available! GitHub: https://lnkd.in/gvYUqhs Use Cases: * As a general purpose Enterprise database that supports Objects persistence. * As an alternative to ElasticSearch or Solr for "search" intensive applications & as a high performance Database combo. * As a blobs(media, etc...) storage with "rich search" capabilities. * ACID, two phase commit transactions for general data quality! * Masterless(or all masters!) thus, hotspot free database servitude, a.k.a. - horizontally scaleable db system. * Etc... many more, limited only with your imagination. :) The library is written in Golang and thus, any Golang application can use it as is. One can write a web service or micro service and make the functionalities of the library(or with your application logic added in) available to other applications. Open Sourced, MIT license. :)
GitHub - SharedCode/sop: M-Way Trie for Scaleable Objects Persistence (SOP)
github.com
To view or add a comment, sign in
-
Horizontally Scaleable Object Store V2 beta 2 is now available! GitHub: https://lnkd.in/gvYUqhs Use Cases: * As a general purpose Enterprise database that supports Objects persistence. * As an alternative to ElasticSearch or Solr for "search" intensive applications & as a high performance Database combo. * As a blobs(media, etc...) storage with "rich search" capabilities. * ACID, two phase commit transactions for general data quality! * Masterless(or all masters!) thus, hotspot free database servitude, a.k.a. - horizontally scaleable db system. * Etc... many more, limited only with your imagination. :) The library is written in Golang and thus, any Golang application can use it as is. One can write a web service or micro service and make the functionalities of the library(or with your application logic added in) available to other applications. Open Sourced, MIT license. :)
GitHub - SharedCode/sop: M-Way Trie for Scaleable Objects Persistence (SOP)
github.com
To view or add a comment, sign in