TomHebert

My software speaks for itself.

[TomHebert @TheWayForward]

You obviously were not in big city heavy traffic because you would still be there. In heavy traffic in Phoenix, my car fails to get to the exit about 10% of the time. It waits too long to get over and the other drivers close ranks.

In addition if you have to turn left onto a busy street without the benefit of a light you are toast. I swear to God it will wait until there are no cars in sight to make a move. In the meantime the drivers behind you start blasting the horn

In light traffic, and long-range trips it’s not so bad.

The snowbirds are arriving and the traffic is growing. I’m stopping my subscription until they go home.

[TomHebert @TheWayForward]

Vote Democrat. Go broke.

[TomHebert @TheWayForward]

@Oia__1 We didn’t have lift gates in the 79s

[TomHebert @TheWayForward]

@elonmusk @DogecoinNorway How much wort can I get done for $300 per month?

[TomHebert @TheWayForward]

The only pole that matters is this Tuesday.

[Mark R. Levin @marklevinshow]

Ignore the polls!  They’re a pointless waste of your time! JUST VOTE!!

[TomHebert @TheWayForward]

Knowledge is power, especially when you improve performance.

[Meg @MegOfficiall]

I stood up. I said, "Can I?"

He stepped aside.

I fixed it in about two minutes. Then I finished the presentation for him.

The directors asked a lot of questions. I knew the answers.

Afterwards, he came to my desk. He didn't say anything for a while.

Then he said, "I'm sorry about what I said."

I said, "I know. That's why I did the course."

He asked if I'd train the team. All 14 of them. Including him.

I said yes.

Now he calls me before every big meeting.

Last week, he asked me what I'd do if I were him.

I said, "Spend $40 and a weekend before you make a speech."

[Meg @MegOfficiall]

I stood up. I said, "Can I?"

He stepped aside.

I fixed it in about two minutes. Then I finished the presentation for him.

The directors asked a lot of questions. I knew the answers.

Afterwards, he came to my desk. He didn't say anything for a while.

Then he said, "I'm sorry about what I said."

I said, "I know. That's why I did the course."

He asked if I'd train the team. All 14 of them. Including him.

I said yes.

Now he calls me before every big meeting.

Last week, he asked me what I'd do if I were him.

I said, "Spend $40 and a weekend before you make a speech."

[TomHebert @TheWayForward]

@MrB_guy @SBakerMD How did that work out for Steve Jobs?

[TomHebert @TheWayForward]

@SBakerMD Would like to see additional lines showing stent placements and average BMI. Multiple charts filtered for age groups might prove interesting as well.

[Deep Leaks @DeepLeaksHQ]

Nothing screams TRUE SOCIALIST like:

-A millionaire who owns 3 homes
-Arriving in a huge SUV
-To his private jet
-To fly out and give a paid speech
-On the evils of capitalism and fossil fuels

Am I right?

[TomHebert @TheWayForward]

@BLKMDL3 I’m still on 14.1 Lite. I wonder if issues with the newer releases could explain the slow rollouts.

[TomHebert @TheWayForward]

@Mindsparkx__ 11

[TomHebert @TheWayForward]

Am I the only one who can’t seem to get into the Amex Centurion Lounges? The wait times make it a waste of time. By the time you get in it’s almost time to leave, and they are so crowded you can’t do anything anyway.

[TomHebert @TheWayForward]

Put your jealousy in a sock. Work your ass off and earn enough money to get a $5k check. Don't spend everything you make and invest prudently. You too will retire comfortably.

It's your choice. Only losers would choose to steal from those who did.

[Barbell Financial 💪🏻💰 @BarbellFi]

Boomers with $4 million in assets

Paying $200/month for Medicare

Collecting $5k/month social security

All funded by millennials who can’t afford to buy a house or get sick 😳

[TomHebert @TheWayForward]

@mathwithsanni .25

[TomHebert @TheWayForward]

@DrIrumch Only a genius, really?

[TomHebert @TheWayForward]

@sila__2210 16

[Brivael Le Pogam @brivael]

I’m French. I want to talk to Americans who are about to vote Democrat. Not to insult you. To warn you.

I come from your future.

In France we did everything your progressive politicians promise. Free healthcare, free college, generous welfare, strong unions, heavy regulation, high taxes on the rich, a state that takes care of everything. Public spending close to 57% of GDP, one of the highest on the planet. On paper, it’s the dream.

Here’s what it looks like from the inside. France hasn’t passed a balanced budget since 1974. Our debt is above 3,300 billion euros. Interest on that debt is becoming one of the biggest items in the national budget. Our hospitals are collapsing despite record funding. Our schools rank lower every year. Young people with degrees can’t afford an apartment in the city they were born in. Our best engineers leave for London, Zurich and San Francisco. And the rich you wanted to tax? They left too, and took the jobs with them.

The promise was protection. The result is stagnation.

The worst part is that nobody in France voted for decline. Every single step sounded generous, compassionate, reasonable. One more program. One more regulation. One more tax to fund it. Each step alone makes sense. Fifty years of them, and you wake up in a country that can no longer build a nuclear plant on time or keep its streets safe.

I love America because it’s the one place on earth where people still believe they can build something from nothing. I came to Silicon Valley as a self-taught kid and it changed my life. That spirit is the most precious thing your country has.

Before you vote, ask yourself one question: is the program you’re voting for making America more like America, or more like France?

Trust me. You don’t want to be France.

[TomHebert @TheWayForward]

Maybe kick the can down the road and use an unsigned integer. Also, a number of high level language runtimes use more complex representations. Internally on one project we chose to use the number of decimilliseconds since the birth of Christ stored as a 64-but uint.

[Massimo @Rainmaker1973]

The year 2038 problem: a potential digital catastrophe

The Year 2038 problem, also known as the "Y2K38" or the "Unix Millennium Bug," is a digital time-related issue that is set to affect various computer systems and software applications in the near future. Unlike the well-known Y2K problem, which revolved around the rollover from December 31, 1999, to January 1, 2000, the Year 2038 problem is centered on the representation of time in many digital systems. In these systems, time is often recorded as the number of seconds that have elapsed since the epoch time of 1 January 1970, stored as a signed 32-bit binary integer. This encoding method, while efficient, has a critical limitation: it cannot accurately represent times beyond 03:14:07 UTC on 19 January 2038.

To understand the Year 2038 problem, we must first grasp the concept of epoch time. Epoch time, also known as Unix time or POSIX time, is a system for tracking time in computing. It represents time as the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 (not counting leap seconds), often stored as a signed 32-bit binary integer. This format was widely adopted across various operating systems, programming languages, and applications because of its simplicity and efficiency in computation [1].

The root of the Year 2038 problem lies in the limited range of a 32-bit signed integer. A signed 32-bit integer can represent values from -2,147,483,648 to 2,147,483,647. This means it can represent 2,147,483,648 seconds, which is approximately 68 years. Counting forward from the epoch time of 1 January 1970, we arrive at 19 January 2038, 03:14:07 UTC. Beyond this point, the integer overflows, causing time-related calculations to behave erroneously [2].

The Year 2038 problem has significant implications for a wide range of digital systems that rely on 32-bit epoch time representation. One of the most critical sectors affected is embedded systems, which are pervasive in modern life. These systems can be found in medical devices, industrial control systems, transportation, and more. For example, consider the use of embedded systems in air traffic control. If these systems are not updated to handle the Year 2038 problem, it could lead to catastrophic failures in air traffic management [3].

Moreover, financial institutions and banking systems, which rely heavily on precise timekeeping for transactions and record-keeping, are at risk. Incorrect timestamps could lead to financial discrepancies, regulatory violations, and legal disputes. This poses a threat to the stability and integrity of the global financial system [4].

Mitigating the Year 2038 problem is a complex task that requires a concerted effort from the global tech community. Several approaches have been proposed and implemented to address this issue.

One approach is to transition to a 64-bit epoch time representation, which would provide a much longer time span before the integer overflows. While this is a technically sound solution, it requires significant changes to existing systems, including hardware and software upgrades. Furthermore, it does not entirely eliminate the problem, as it merely postpones it to a much later date [5].

Another approach involves using alternative timekeeping systems that are not subject to the 32-bit limitation. Some systems, such as the Network Time Protocol (NTP), already use a 64-bit timestamp. However, widespread adoption of such alternatives is a formidable challenge, as it requires coordination across the entire technology ecosystem [6].

As we approach 19 January 2038, 03:14:07 UTC, the risk of critical failures in embedded systems, financial institutions, and various other sectors becomes increasingly real. Addressing this problem requires a proactive and collaborative effort from the global tech community. Transitioning to 64-bit epoch time representation and exploring alternative timekeeping systems are potential solutions, but they come with their own challenges. To ensure a smooth transition and prevent potential disruptions, it is crucial for organizations and stakeholders to begin addressing the Year 2038 problem well in advance of the impending deadline [7].

References:

1] Leslie Lamport, "Time, Clocks, and the Ordering of Events in a Distributed System," Communications of the ACM, 1978.

[2] Markus Kuhn, "The Year 2038 Problem," University of Cambridge Computer Laboratory, 2008.

[3] Charles Perrow, "Normal Accidents: Living with High-Risk Technologies," Princeton University Press, 1999.

[4] Janusz Ordover and Russell W. Cooper, "The Bigness Complex: Industry, Labor, and Government in the American Economy," Brookings Institution Press, 1999.

[5] Brian Ford, "Large Address Aware Programming in Windows," Microsoft Corporation, 2013.

[6] David L. Mills, "Internet Time Synchronization: The Network Time Protocol," CRC Press, 2006.

[7] John K. Ousterhout, "System Performance," Pearson, 1990.

[TomHebert @TheWayForward]

It is like “back to the future “. Before data processing, our system of record was documents. But computers couldn’t handle documents so we distilled them down to journal entries. Then we tried to design databases to contain documents. It’s expensive.

I say we go back to documents. Let AI process the docs, check for policy adherence and handle the journal entries. Flexible and easy to understand.

[Chamath Palihapitiya @chamath]

These are some very important observations from Satya.

As models and harnesses commoditize, intent, verification and evidence will gate how quickly SI permeates enterprises and businesses.

Importantly, you need to implement systems that separate who does the work from those who govern, measure and sign off on it.

This is a new kind of “harness” that will emerge over the next few years. It may become a new system of record over time. One whose entire role is to track “change” and map it back to SOPs, policies, laws and the like.