Hacker Newsnew | past | comments | ask | show | jobs | submit | Throw10987's commentslogin

That seems sane, is there a cohort of engineers pushing for trunk based development?


I think the point is that the Access, Lotus Notes tooling was in largish corporations somewhat ubiquitous.

The experience of this tooling was make a change and it was in production. It was incredibly simple and productive to work with given the needs of the time.

There was also plenty of opportunities to make a mess, but I don't think that has really changed.

Learning was not difficult, you just had to be prepared to spend time and some money on books and courses.

It is not a tooling set you would want to go back to for a bunch of different reasons but it worked well for the time.


> It is not a tooling set you would want to go back to for a bunch of different reasons but it worked well for the time.

I remember using lotus domino at one of my first jobs. There were all sorts of things I hated about it. But you could have a database - like the company’s mail database. And define views on that database (eg looking at your inbox, or a single email). And the views would replicate to a copy of that database living on all of your users’ computers. And so would the data they needed access to. It was so great - like, instead of making a website, you just defined the view based on the data itself and the data replicated behind the scenes without you needing to write any code to make that happen. (At least that’s how I understood it. I was pretty junior at the time.)

Programming for the web feels terrible in comparison. Every feature needs manual changes to the database. And the backend APIs. And the browser code. And and and. It’s a bad joke.

Commodification has a problem that for awkward teenagers to make the same fries every day, we have to ossify the process of making fries. But making good software needs us to work at both the level of this specific feature and the level of wanting more velocity for the 10 other similar features we’re implementing. Balancing those needs is hard! And most people seem content to give up on making the tooling better, and end up using whatever libraries to build web apps. And the tools we have are worse in oh so many ways compared to lotus domino decades ago.

I wonder what the original lotus notes designers think of web development. I think they’d hold it in very low regard.


Believe me it is not laughing in a good way, it is more a nervous laughter with a permanent sinking feeling in the stomach kind of way.

The collective 'we' developed nations have our own set of problems, but broadly speaking from time to time self correct away from polarisation to hopefully enough of a degree.

A unique kind of leadership needs to be allowed to grow in America to stear a less polarised course.


I know, theyre laughing at us because we think our compromisestitution is a feature


In my part of the world that would be inner sheep.


Not 100% sure of the rationale in this case. I imagine it might have to do with everyone who runs an instance needs to maintain an additional storage system along with all the associated costs, which is not just storage alone.

Databases store stuff really well. If get to the level of needing to configure storage for different tiers of access they can do that, it just takes a bit of work. Of course if your blob data is stored in tables that have OLTP data in them, then you have a bit of work to do to separate it out.

This is speaking from recent experience of having to manage random blobs of sensitive data in s3 buckets that engineers have created rather than bothering to put in the main application data store.


Robocopy may be an approximate equivalent for rsync. https://learn.microsoft.com/en-us/windows-server/administrat...


I am chartering a yacht in two weeks and have been busy re-learning how to tie a core set of knots. This is easily the best resource that I have been using with the rest of the crew(aka family)!


I am the most senior engineering IC by position and years of experience at my current company in a 100+ person engineering group. The only problems I deal with are non technical and organisational in nature, despite on paper being expected to code 30 percent of the time.


I’m sorry - I’d advise either making your role better or finding a better team. They exist.


Sound advice - currently going down the path of try to make the role better. It will however be a long journey, so need to work out whether I am sufficiently committed to the path. Also need to work out what the ejection criteria are, regardless of my commitment or not.


And loving it ;)


I find myself coming back to Data and Reality on a periodic basis to remind me that the model is just the model.

https://www.bkent.net/Doc/darxrp.htm


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: