Yes. My first job out of school was as a mainframe programmer on a large accounting application. It was written in COBOL with DB2 on the backside. Online screens were COBOL + IMS + DB2. I learned about what not to do to succeed so much at that and by the time I left that team I was a valuable member of it.
The MVC concept doesn't imply monolith. Eventually the tooling will catch up to the PaaS change. There are already some frameworks like serverless that try to do this, they are just bad at it for now. This is not all the fault of the frameworks either, scalable cloud components are PITA to build and configure.
For example: Lambda forces a specific AWS Linux build of each language it supports, and all default libraries that can be stripped out have been. The build package for each Lambda is small, so all libraries and data have to be zipped down to 50MB or less which completely rules out tons of common libraries.
The concept is really cool, often usable, and incredibly cheap. The platform and tools will get better, and eventually MVC will work on PaaS someday, but for now it is a pain to ride the bleeding edge.
Experienced ASP.NET developer passionate about learning Software Engineering, being an effective team member, and carving out my own little niche in the world.
I enjoy working with jQuery, Angul...
I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
A while ago I used to work on a documentation project for Discord (the modern version of IRC). I have a few (emphasis on few, not many, just few) fond memories of that, but nothing thats really substantial. I've found that it's often hard to have a 'connection' with your code unless it's rather still being used, it's been acquired, or you've been recognised for it - otherwise, it can often seem as though you've just smashing away at your keyboard trying to see if it does anything.
Kinda sad, but hey, that's just how I guess it goes!
My very first project that I was paid for was an online reservation system for sports center. I was using LAMP stack and I basically learned how to program while writing it. It was kind of breaking point in my career, since this was the first time something I wrote made impact on people.
It was developed in 2009 and since then it is running without any major issues (the use case is simple and there really weren't any requirements on improving UI). Call me sentimental, but I recently browsed Google reviews for this sport center and found some people that praised the ability to "easily book a time slot via online reservation system" :).
I created a small (~1kb gzipped) vanilla js module in my previous job to toggle, add and remove class names of any elements that could be selected with a CSS query on click (+mobile support) which was extremely versatile and configurable with data-attributes. It's still heavily in use without any changes and was the reason we could remove jQuery from a lot of simple pages.
Yep. My first real project that got me started with real-ish dev environments and tools and languages.
One of the last people to learn Ruby on Rails from scratch! I miss it a bit, but I never had time to understand it or be part of the community like JS.
Heres the repo, don't judge me! I was 20 or 19. github.com/cucumbur/buzzworthy
Now, I like JS even with the tooling and all.... but i miss not having to do a microservice architecture everywhere and I wish I could use TInkerpop everywhere
Now, I like JS even with the tooling and all.... but i miss not having to do a microservice architecture everywhere and I wish I could use TInkerpop everywhere
That was a big reason I started dev.to. I just wanted to build a Rails app.
A 10 year old HTML page that was changed often to display weather information by hand. Documenting how to update without breaking the HTML to weather professionals was a treat.
The last Oracle data warehouse I built, for a telecom company, is the one I look back on.
I was the sole developer/designer/documenter, and handled everything from requirements through ETL (in PL/SQL) to storage and Business Objects reports.
In the last year I was developing and supporting it, it ran without error 365/24, and had complete documentation in the form of nested data flow diagrams.
Having said that, I don't miss that world. Too corporate, too commutey.
Oldest comments (27)
Yes. My first job out of school was as a mainframe programmer on a large accounting application. It was written in COBOL with DB2 on the backside. Online screens were COBOL + IMS + DB2. I learned about what not to do to succeed so much at that and by the time I left that team I was a valuable member of it.
Awesome
I miss writing web servers with MVC LAMP. I hate micro services and AWS Lambda. It is all better now, but worse somehow.
Do you think things will ever shift back towards the monolith in any way? Or are we trending smaller and smaller period?
The MVC concept doesn't imply monolith. Eventually the tooling will catch up to the PaaS change. There are already some frameworks like serverless that try to do this, they are just bad at it for now. This is not all the fault of the frameworks either, scalable cloud components are PITA to build and configure.
For example: Lambda forces a specific AWS Linux build of each language it supports, and all default libraries that can be stripped out have been. The build package for each Lambda is small, so all libraries and data have to be zipped down to 50MB or less which completely rules out tons of common libraries.
The concept is really cool, often usable, and incredibly cheap. The platform and tools will get better, and eventually MVC will work on PaaS someday, but for now it is a pain to ride the bleeding edge.
tbh, no. tons of legacy code out there that should be replaced.
We have a winner here 🦄
Most greenfield projects I've worked on. Starting something from scratch is always very exciting and memorable.
A while ago I used to work on a documentation project for Discord (the modern version of IRC). I have a few (emphasis on few, not many, just few) fond memories of that, but nothing thats really substantial. I've found that it's often hard to have a 'connection' with your code unless it's rather still being used, it's been acquired, or you've been recognised for it - otherwise, it can often seem as though you've just smashing away at your keyboard trying to see if it does anything.
Kinda sad, but hey, that's just how I guess it goes!
My very first project that I was paid for was an online reservation system for sports center. I was using LAMP stack and I basically learned how to program while writing it. It was kind of breaking point in my career, since this was the first time something I wrote made impact on people.
It was developed in 2009 and since then it is running without any major issues (the use case is simple and there really weren't any requirements on improving UI). Call me sentimental, but I recently browsed Google reviews for this sport center and found some people that praised the ability to "easily book a time slot via online reservation system" :).
I created a small (~1kb gzipped) vanilla js module in my previous job to toggle, add and remove class names of any elements that could be selected with a CSS query on click (+mobile support) which was extremely versatile and configurable with data-attributes. It's still heavily in use without any changes and was the reason we could remove jQuery from a lot of simple pages.
Yep. My first real project that got me started with real-ish dev environments and tools and languages.
One of the last people to learn Ruby on Rails from scratch! I miss it a bit, but I never had time to understand it or be part of the community like JS.
Heres the repo, don't judge me! I was 20 or 19.
github.com/cucumbur/buzzworthy
Now, I like JS even with the tooling and all.... but i miss not having to do a microservice architecture everywhere and I wish I could use TInkerpop everywhere
That was a big reason I started dev.to. I just wanted to build a Rails app.
A 10 year old HTML page that was changed often to display weather information by hand. Documenting how to update without breaking the HTML to weather professionals was a treat.
The last Oracle data warehouse I built, for a telecom company, is the one I look back on.
I was the sole developer/designer/documenter, and handled everything from requirements through ETL (in PL/SQL) to storage and Business Objects reports.
In the last year I was developing and supporting it, it ran without error 365/24, and had complete documentation in the form of nested data flow diagrams.
Having said that, I don't miss that world. Too corporate, too commutey.