systematical

Oh God. This is what is happening at my work. We have an API that has 200 write users and a public front-end that can do reads. None of it is heavy though, with most writes occurring for a month in the Winter and a month in the Fall. In the unlikely event of heavy write loads we could just scale up CPU/RAM for those two months. Any read load be solved with cache or spending time on the worst offenders in SQL. The Lead Dev is gung-ho that it MUST be a micro-service with K8, Kafka, and I'm sure a bunch of other shit we don't need for what is the same application that has been being written for half a century. Data in/out with business logic applied. The entire API has about 8 paths, with your basic HTTP methods for each. Its probably the smallest API I've ever worked on.

The positive for me is I am learning a bunch of stuff during the process. The negative for the project is he expects developers with no previous skillset in this space to design all this new (for us) tech without introducing technical debt. The downside for the client is...well guess.

It's sad. I am rewriting a problematic legacy application and creating a whole new one. I guess I can put K8 and the kitchen sink on my resume when I look for a new job just before this thing implodes on release though. I just wanted to write clean code man, thats all. There is a sadistic part of me that wants to grab some popcorn and see how this explodes in his face...there is also a part of me that wants to be proved wrong...I hate this job.

I did this for a company of the same size. I spent 15 minutes each morning (during coffee) answering important emails. The rest I left for when i got back.

The most recent MVP I created: CakePHP, MySQL, jQuery (UI/UX called for minimal dynamic UI IMO), and bootstrap. Very boring full-scale MVP released in under three weeks. I designed as client-server in case the need arises to go SPA with React down the line or go with a mobile app option, but I doubt the need.

Non-tech co-founder was worried from what he read on PHP etc.... Non-tech co-founder is not worried today.

PHP devs make good money, maybe not what their peers in "good" languages make, but a good Senior PHP dev is making six figures in most markets these days.

Good thing we have the de-escalator in chief.

Uh huh...

Amazon, Expedia, Grubhub and others are just middlemen sucking blood from small businesses and consumers.

Is there something that is annoying you? Do you know there is a better way to do it?

I've spent part of the pandemic automating OpenAPI spec with minimal annotations needed for an API. I was annoyed that the existing solutions wanted more annotations than actual code, when all the information OpenAPI/Swagger needed was already right there in my code. Just an example.

I think the biggest problem with cubicles is they seemed to either come in the colors of prison gray, 1980s beige, or 1970s green. Cubicles were fine for all the reasons this poster mentioned. Just try not to make them look like despair is all. And yes, fuck open design.

A good reason to not use your checking or debit cards. I only use my credit cards, then pay them off every month before incurring interest. Makes scanning your checking account for fraudulent charges easy. I report my credit cards lost once a year and get new ones in case those have been unknowingly compromised, kinda like changing my password.

https://github.com/cnizzardini/cakephp-swagger-bake also combining various other cake libraries into a competitor to api platform for those who prefer to write code instead of comments (annotations) and YML.

The Yang Gang is very active online and offline.

Source: I'm Yang Gang

Google is pretty much taking your shit nowadays and there is nothing you can do about it. That shit is either a company you built or a product of theirs that you used. They are not a search company, they are a conglomerate. They'll buy you or break you. It's funny when they fail though isn't it? Remember Google+? Who lead that initiative? What a travesty that was. Outside of Gmail, Google's UIs really do suck.

But back to the point. There really isn't anything wrong with what they are doing, they are a typical business. Again, nothing wrong with that. They do stuff for their own self-interest. They are not your friends. Organic search results get in the way of advertising.

API Platform, a Symfony bundle (thats a library, but I guess they thought bundle sounded better), gives you a pretty verbose docker-compose.yaml to get started. I looked at it, shook my head and downloaded it.

https://github.com/api-platform/api-platform

I'm sure they had good reasons...or they just wanted to say hey, we're modern.

I agree, though for local development environments docker is pretty handy for getting the full stack up. Especially if you just came aboard.

But this is the name of the game. More and more complexity. I am not sure how green engineers manage to learn everything. Woof

I thought I was just going crazy. I asked friends and they didn't agree. It actually looks at lot like duck duck go. I never liked their UI, but if I am faced with a privacy destroying goliath and a terrible UI or a privacy-protecting company with a horrible UI...well I think the choice is obvious.

Google took queues from Reddit and fucked their UI. That's why those top UI/UX grads get paid the big bucks I guess.

COL eats it away, the extra salary is not worth it. I'm sure its the same for SF, NYC, and other similar cities.

I didn't say I had a low salary. As a single guy living by himself, my salary is above or near most of the median HOUSEHOLD incomes listed in that article. However, the cost of living here eats it away. Compare a city like Philly to DC for instance. Last I checked, COL is 27% cheaper in Philly and salaries are only 3% below DC.

Which goes back to my original point: "Yuck. You actually lose money working in DC, the salaries aren't even worth."

The article mentions DC and I'd just like vent about how miserable a place this is to live in. I see some people spend 10 hours a week and often more just commuting to work. It's overpriced. And when you look at the state of IT in the federal government you realize why this government fails so badly at non-tech things.

I'll be running away from the major cities as fast as possible as soon as possible.

Yuck. You actually lose money working in DC, the salaries aren't even worth.

Shouldn't that return an HTTP 451?

I have ten of the next big things sitting on my computer anywhere from 10%-80% finished. Some are using new technologies, but many are using tried-and-true. It didn't matter.

I've been racking brain cycles the past few weeks trying to figure out how to solve this problem.

- Amount of dev time needed to ship an MVP

- Lack of a business partner

- Not having a pilot customer lined up

- Getting old

Those are some of the issues I see as a far bigger hinderance than any tech stack stuff. Shit, when is the last time (have I ever) tried doing a no-code MVP. Not always possible, but I'm sure somewhere in that stack of unfinished projects I could've come up with a no-code or very limited code MVP...

I'm hoping some sanity is brought to front-end development. I had a project which legitimately did require a slice of the site to be SPA. I didn't do the full site, just the piece that needed it. When I looked at using React I was confused that it seemingly didn't want me to actually write HTML. Maybe I misread something, but it seemed like it wanted me to return HTML from JavaScript...this made little sense to me. I ended up using VueJS because it was far easier to learn. It did the job.

Webpack certainly is confusing too. I did a side project with some webpack and es6 stuff. It was kinda fun, but man, front-end development has sucked forever. I remember back in the day having to fight with IE6. Here we are, thirteen fucking years later and shit seems to have gotten only MORE complex.

I look at server-side programming for comparison. PHP for instance certainly is more complex with some of the frameworks you can use now and of course composer. But those are WAY simpler than the shit I had to deal with when coding the front. I just don't understand how things have gotten more complex on the front-end, brutal.

It got me thinking about playing around with WebAssembly for building front-end applications. Maybe that doesn't fit all use-cases and maybe the grass is always greener, but I wonder if programming in sane ecosystem would be the sane thing to do...?

Put me in the camp that if there isn't a use-case slapping me in the face, choking me, and yelling at me to do a SPA then I'll avoid the shit like a plague. I'll just go with server-side render pages and sprinkle in some very basic jQuery as needed. I actually did that for a CRM two years ago and the thing is so damn simple to program in, because JavaScript is only used if it ACTUALLY provides a benefit to the user. There is a site-wide script that is maybe 100 lines of code. Then some page-specific things that load in stuff using RequireJS, but the most complex JS out of those is maybe 300 lines. The vast majority of the site doesn't really use much JavaScript. Just plain old MVC.

As always, please BURN YOUR JAVASCRIPT STICKERS.

I had the same thought

Let's be honest even in our current technologies of choice the product rarely ships. But I get your point.

Yeah I could see that happening. They heard the buzzword.

Do you consider the press part of society?

Facebook, Twitter, and Google. I think they are integral. Sure, you could replace them with different names, but the result is the same.

I've never had a business-person come to me and say "you are building a SPA", or "we are using React." Now, they have come to me with some brilliant and also ridiculous ideas, and I've done them all, but none of those dictated a particular engineering solution.

I never got on the SPA bandwagon, unless the UX required it. But then, I'm old. Burn your JavaScript stickers.

I'm glad I'm not alone. Burn your JavaScript stickers.