Post #31785

27242b556317d204596bb20c828b2ed7c843d7fa6bd601e88b0688f001b442da
218db6250209a822eb55ff6f1a0c1841bbd932ef110d6ed62f755e3fdb4b388e
e2c61429397da55a5ee7749088023feb12e0e8e261dfeba32ee7c0794f9a12f8
Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

{"entry_date":1613405191,"post_data":{"edit_count":1,"last_edit_date":0,"last_edit_user_id":0,"message_sha512":"7e8d7186366be512639a4fcb1712083c8a301e3a64f86eaf82c9395d9a7ab79bccfeebf4218d4e4a4773290a9b7fafb1cbada8596b496f447131c46cc3e9b3e5","node_id":115,"post_date":1613405168,"thread_id":5666,"user_id":2},"post_link":"https:\/\/forum.factomprotocol.org\/threads\/sphereon-bv-niels-klomp.5666\/post-31785"}
The entry content as it exists in the database. This should be verified against the blockchain entry.
[Sphereon BV] Niels Klomp
Hello Niels.

Clay, Who, and Luap worked hard to make trash code reasonably stable and add some TPS to the network. As far as I know, none of them are working on the code in any meaningful way. I've seen proposals that others start to take up that slack. As we both know, all developers are not created equal. The Factom codebase is still a mess and it will take a good developer months to figure it out. As such, there may be an understandable desire to bring back some people who are familiar with the codebase but don't write the best code which could result in the network taking a step backwards. This creates risk for outside entities like my own that hope to utilize the protocol.

What steps would you take to ensure that only quality, well tested code makes its way to production?
This is the raw content, without BBCode parsing.
Top