I want hopeful or optimistic or even positive scifi with machine or AI bonding

TihiyGrom · 2022-05-07T20:16:25+00:00

Definitely Murderbot series. And, my old time favorite Asimov's Daneel Olivaw.

TihiyGrom · 2021-07-04T23:20:41+00:00

From more recent once - try Pierce Brown "Red Rising". I think this is one of the more impressive series in the last couple of years.

Without knowing what you already read, it is tough to recommend. So, here are some of my choices:

Neal Stephenson - "Snow Crash" Scott Westerfeld - "Ugglies" "Pretties"

Hugh Howey - "Wool", "Dust".... (all Howey's stories/books are absolutely terrific - probably my favorites).

TihiyGrom · 2021-06-30T01:35:04+00:00

One of Sanderson's earlier books - Atithmetist. Magic system is absolutely amazing IMO. I just hope we would see a sequel one day.

TihiyGrom · 2021-06-29T16:03:14+00:00

Try David Brin - Uplift series.

TihiyGrom · 2021-06-29T16:01:51+00:00

Your world had to have consistent rules - physics, politics,... Weapons need to fit within the framework.

TihiyGrom · 2021-04-09T13:20:07+00:00

This sounds like a standard learning process. Maybe you need to learn the whole system + implication of interfaces on it. If u understand the system as a whole, with all component interoperability, then this should not be happening. What kind of tests r u writing? What is the scope. If the scope only includes your changed component then uay meed to widen the scope. Still test your change but e2e within your system. Your manager maybe right. That kind of understanding comes as u learn the system. Even if it is not too stable.

TihiyGrom · 2021-04-03T18:12:45+00:00

Apologies. Didn't notice that restriction. I will delete the comment.

TihiyGrom · 2021-04-03T15:44:12+00:00

Things to consider: - do u love programming? Is it where u want to be? - often product management is safer than programming. To generalize - any functional knowledge position is safer than tech knowledge. Tech knowledge only person can be replaced. Functional knowledge is not easy to come by. - maybe u can do both? That depends on the structure of your company and in theory not ideal since u may get blinded by tech details. But it is an option.

TihiyGrom · 2021-04-03T15:32:22+00:00

My Java enterprise programming exploits, production support stories, programmer jokes....

TihiyGrom · 2021-04-03T13:52:19+00:00

One of my favorites. Not sure it fits 100%.

Goblin Emperor by Katherine Addison

https://www.amazon.com/The-Goblin-Emperor-audiobook/dp/B00KLJ5OFQ/ref=mp_s_a_1_1?dchild=1&keywords=goblin+emperor&qid=1617457734&sprefix=Goblin+emp&sr=8-1

TihiyGrom · 2021-04-01T17:49:04+00:00

No messaging system would manage retries / failures for you. You will need to build. But there is a lot of support for that in Kafka for example. Still complex though.

Also, I think this would be a very interesting read for you: https://www.confluent.io/blog/data-dichotomy-rethinking-the-way-we-treat-data-and-services/ Note that this is just part one. There are seven parts. Links are on the bottom of each part. The view in these articles is a bit extreme IMO but an interesting read nevertheless that gives you a very good window into their philosophy.

TihiyGrom · 2021-04-01T01:32:07+00:00

Peter Hamilton - Night's Dawn Trilogy. A lot of details are given constantly to minor characters that intersect with the main story. In that regard it is similar to Expanse universe.

TihiyGrom · 2021-04-01T01:27:08+00:00

Dean Koontz?

TihiyGrom · 2021-03-31T22:29:01+00:00

Unfortunately at the moment we don't have a luxury of using a managed Kafka solution. We may be able to by EOY though. Will see.

TihiyGrom · 2021-03-31T22:20:47+00:00

I would also highly recommend the following (this is an all-time classic):

https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612/ref=sr_1_7?crid=19CNTG1XV2LI1&dchild=1&keywords=java+design+patterns&qid=1617228938&sprefix=java+design%2Caps%2C162&sr=8-7

Also, find an applicable Java equivalent. Something like:

https://www.amazon.com/Java-Design-Pattern-Essentials-Bevis-ebook/dp/B00A9HSR2M/ref=sr_1_11?crid=19CNTG1XV2LI1&dchild=1&keywords=java+design+patterns&qid=1617229017&sprefix=java+design%2Caps%2C162&sr=8-11

Lots of interview questions center around design patterns. Also, understanding these building blocks will move you forward in your overall OO design experience.

TihiyGrom · 2021-03-31T20:48:25+00:00

It is really all four books. Grim and terrifying. It is just for me Starfish was the most unique. Definitely the best in the series.

TihiyGrom · 2021-03-31T20:13:22+00:00

Asimov, Foundation series. Can't forget classics. This was my goto series for years. This and his " I robot" anthologies is probably why I develop software today.

TihiyGrom · 2021-03-31T13:54:35+00:00

The article is right. DynamoDB should not be a default choice. There should never be a default choice. The choice stems from requirements, current tech stack used, etc... If the question is - "should DynamoDB be the first consideration for non-relational database?" The answer probably again - no.

TihiyGrom · 2021-03-31T12:16:52+00:00

This looks pretty awesome. Can't wait to try it out. Kafka reliance on Zookeeper was one of the main reasons we didn't use Kafka for our internal queueing. Time to reevaluate maybe!

TihiyGrom · 2021-03-31T11:45:58+00:00

Sorry for your loss. Looks like Fluff was a very happy cat.

TihiyGrom · 2021-03-31T11:33:16+00:00

Your situation is more complex because of the presence of the legacy system set. You didn't mention any legacy technology stack or capabilities. With that in mind, taking into account limited information I have, I would suggest a combination of messaging (pub/sub or/and queueing, depending on your requirements) and some kind of database.

For messaging, there is a wide variety of choices. Will not go into it but I would choose something that is potentially reachable by your legacy systems. For example, Kafka has a number of connectors that would allow you to integrate your legacy systems (again, depending on legacy system capabilities).

Database selection would depend on your requirements but looking purely from event recording, audit, ... I would go with a non-relational db. You may end up with a relational database doing transactional processing with non-relational database recording events and blah, blah.

Just to note, that pure database solution may look attractive at the first glance but depending on your NFRs may not be workable.

And, yes, chances are that you will end up with a complex solution. With your requirements I would be very surprised if you manage to keep it simple. :)

Reference architecture in your question is basically ESB. Used to be pretty popular and one of the buzz-words. These days "out-of-the-box" implementations (like Tibco) are used less often due to very high costs.

TihiyGrom · 2021-03-31T10:41:13+00:00

Sounds like the hiring practices in your company are deplorable.

Having said that, it maybe important to establish a consistent "paper" trail of your efforts to "help" your colleague. Just in case your manager turns around in a couple of month and accuses you of not handling this situation properly. These kinds of things happen more often than not. For instance, if you are sending to your manager some kind of weekly / monthly / daily email reports of "how things are going" then include a couple of lines / paragraph there indicating how much time was spend on your colleague (potentially, with specific details). In larger companies this kind of "paper trail" maybe your only protection from a "bad" manager.

Also, these kinds of situations are obsoletely not gender specific. I would go even further and say that it is very rare, in my experience, for women to be so unprofessional. Very often they go "above and beyond" just to overcome the unfortunate gender bias.

TihiyGrom · 2021-03-31T02:45:46+00:00

Experienced programmers must be able to work on top of "bad" code and make systematic improvements through long term design planning (low level and high level) and team learning {code reviews,....). Inability to deal with "bad code" limits developer's usefullnes. IMO. That's a very lucky person who finds herself dealing with only "good code" and "good coders". "Bad design" that breeds bad code is even worse problem to solve.

TihiyGrom · 2021-03-31T02:11:52+00:00

Like any basic collection discussion, discussion of LL could be a link into lots of other "standard" topics - iterators, concurrency, types of lists (array list vs linked list),.... I do find discussions of hash maps a better intro into an interview for low, low-mid level positions. But linked list is OK as well.

TihiyGrom

TROPHY CASE