Me:

- Uses i3wm, elinks.

- Uses elementary, arch, and xubuntu interchangeably.

- Has ansible playbooks to automate my environment setups whenever I feel like swapping distros or get a new machine.

- Almost exclusively use my dinky little Acer laptop.

- Uses vscode with VIM mode for larger projects.

- Uses vim for simple edits.

- Uses Operator Mono.

- Uses Firefox for general browsing.

- Refuses to use mouse, will use ctrl + f to focus on elements and enter for navigation without a mouse.

What am I?

@ThaOneDude Overwatch is key to a great hack.

@SHA-16384 decided to open source my project from work and decided to write a few tools and sites to help me learn new frameworks haha

I once deleted a client node for a company contracting over 100,000 grand on accident. On initial attempted restore caused our event message broker to shit the fan. Took our top software engineers nearly a month to resolve the underlying cause, and we were forced to give them free use for the next year.

Hoping for the best mate, cheers.

@skynet I'll give it a whirl for my React todo!

WordPress is legacy software. In the ever changing climate that is web development, WP has no place. Allow me to explain,

WP was designed for a genetic lamp stack, and designed in a linear fashion. The only appraisal I ever hear for WordPress is over it's robust plugin system, which doesn't stack up to the features of many modern css and JavaScript frameworks.

Granted you can write over your templates using anything you please, you're still locked to the WP ecosystem.

Now I'm not saying WordPress is all so awful, especially with the new wp2 REST api. It still not may be a bad choice for bootstrapping or prototyping a simple SPA, but it's just not a viable solution for modern web applications. There's simply too much overhead.

That all being stated, there are far too many security flaws. Not because it was designed so poorly, but because there's security in obscurity.

Finally, if you have to depend on WP to build websites or apps, you should reevaluate your skills.

@Eariel Sounds like a horrific experience, I wouldn't lost my sh**.

z-index: 9;

a modal is now visible above the standard layout

z-index: 99;

a modal is now layered atop the header

z-index: 999;

a modal has become "woke"

z-index: 9999;

a modal has transcended into the 21st dimension

If you ever get comfortable enough with the new WP api, it's actually a very nice way to hack together SPAs and simple web apps. By this I mean building your front end from scratch but using WPA for data storage and media handling.

I pumped out a real time UFC score card / betting app in less than a day using WP and But. WP is also very easy to dockerize and plays nicely with NGINX.

That being stated I'd never recommend actually building anything with WP's CMS.

Vue is key. Vue is life.

@gberginc We have weekly meetings and I bring up my concerns consistently to no avail. I'm not going to beat around the bush, I'm about getting sh!# done. I don't think we should spend a week working on a feature that we can pump out in a day and iron out in two. I'm all for peer review, and for a team effort. But when you're team is riding a donkey on a nascar track, it's frustrating.

Addressing the unit tests, it should be common place to unit test EVERY exported client package, otherwise we run into scenarios where things don't work the way we expect them to or just don't work at all. In light of this, I've resolved a greater majority of our utilities that was butchered while adding "hot fixes".

As far as pep8/linting our Python code, why wouldn't we? We should ensure all of our code is consistent and maintainable. Otherwise, what's the point?

Regarding waiting until he left to get work done, to give some context --

I've been bringing up updating our codebase for the past 2 months in every single one of our weekly meetings. Every time I was met with the same response, "we can't just refactor all our code out of no where, we need to all agree and set aside a week to do so". It was *never* going to be done if I didn't take the initiative.

As for my code being too complex, if you're a hired Python dev and don't know what list comprehension is, there's a problem.

@dontPanic that's what I'm going to find out, the now I think about it the more ridiculous the situation isn

So I finished the book, was pretty informative. Can someone explain the O'Reily meme?

Don't get me wrong, in a situation where I'd like to learn a specific framework like riotjs or tool like ansible I would go directly to the docs. But this book is more of an intro to ux and how ux can completely change use cases for applications.

She shells together a lot of popular tools for this intro with some really nice examples and real world use cases.

I guess what I'm looking for out of this is real world application to UX and how to approach it correctly, rather than just learning how to use css animations and D3.js

It's very well rounded, she covers using d3.js for data visualization, basic css keyframe/animation semantics, greensock for animating svgs and a lot more

Docker or rocket

Depends on the scope of the project and what you're trying to solve. Node is my goto because it's incredible community and seemingly limitless modules and frameworks available. If you want to try something new, give meteor.js a shot. My other quirk with JavaScript is everything in one language.

Rails has been on a decline for a while, Codeacademy just trashed it, Codefights is ditching Ruby, and it's too opinionated for modern web apps or services.

Flask/Django is a solid choice, but if you're planning to scale I would steer away unless your going with a microservice architecture.

GoLang is incredibly fast and offers concurrency better then any other language or platform out there. Google, as well as numerous other tech giants have began adopting it.

C++ with Pistache if your going for a RESTFUL or CRUD backend and want a challenge.

I'm 21, I'm a full stack engineer who also co leads our end to end automated testing team. No formal education, I have experience with C++ ( actual std not MS ), C, C#, Java, FPC Lazarus, JavaScript ( primary focus ), Python ( secondary focus ), and GoLang ( learning ).

I have experience with both agile continuos integration/deployment. I'm up to keep with industry standards like Docker, Vagrant, and AWS, Chef/Ansible, and other fascinating tools.

I've set up my own independent CI systems for personal projects namely Jenkins and Concourse, I have basic sysadmin experience including NGINX/Apache.

I have a very extensive background reverse engineering and creating embedded systems.

I know and use both relational and NoSQL databases on the daily.

What I can tell you after interviewing members for both my teams is that formal education is shite. You only learn programming basics and theory, with a focus on algorithms in most schools. They don't prepare you at all for the real world.

Yeah, dumped a virtualized copy of my target binary after it was decompressed before the anti cheat hid it. Used IDA and Radear2 to piece everything together. Used CE to patch up the detections, and wrote a detour to loop and emulate the heartbeat for the anti cheat.

If it's not for a .NET induced language, just stick to VSCode. Even then, there are tons of great plugins available for C#.

From experience; learn vagrant. You can spin up workspaces on the fly, can also be useful for small dev teams.

@InEdited hipsters. NPM and Yarn are both superior to compose, pip, and gems. The workflow with JS projects is so streamline.

You can bootstrap an app in an hour if you know what you're doing. You also have so many super sets at your disposal like Coffeescript for Python and ruby devs, and TypeScript for C++/C# devs.

It's heavy, even if you're using mono -- using .NET on a non windows OS just feels weird. The architecture for basic applications is fucking prehistoric. And finally, there are numerous better platforms available.

I don't see why in this day and age, any web developer (Frontend, backend, or full stack) wouldn't default to Node. One language, one dependency management system.. Everywhere vs architectural bullshit.

Don't like vanilla JS? Use a superset. i.e.; TypeScript

If we're talking about performance, GoLang outperforms the two in both concurrent requests and latency. What nodejs has over Python in general, is its async nature -- making it not only easier to handle more concurrent requests, but much more reliable.

At the end of the day, it really all comes down to use case and scalability, but from local tests and what I've gathered, Python is a nightmare for handling concurrency.

I should also add our data tier service is coupled with multiple other services, further explaining my rant.

If you're going to write JavaScript on the client end, why not just use it on the backend too? To be honest the use case for Node.js has evolved so much over the past years, I can see why it would be difficult for new developers to understand.

Node.js can be used to both create your server or micro service, as well as your entire bundled front end application. It's as flexible as any web developer would need it to be, and the monolithic Javascript community makes it easy to find any one plugin you need for any of the never ending frameworks available.

Knowing Python, C, C++, Java, and the .NET suite; I still believe JavaScript to be the greatest language/platform available to developers today. Don't like it's dynamic type nature? Use TypeScript. Are you a ruby or Python hacker? Use Coffeescript.

It's the best of all worlds.

PHP development on a standard lamp stack is an anti-pattern. Even if properly using composer or other dependency management systems, it's a flaky language to build off of. It teaches bad practices with absolutely no standards. PHP7's speed is quite appealing, but my primary concern with modern web development is; if you're going to write JavaScript anyways, you may as well just use it on the server as well.

Of course, I understand that in a multi service architecture you're going to be using a plethora of different languages on different systems, but it still doesn't excuse having to write in an extra language if not necessary.

Needless to say, if you're just building an API; you're better off learning NodeJS or GoLang if you're after performance.

Finally, I don't hate PHP, I just feel it has no place in modern web development. I can go on for days, but I also recognize great frameworks like Symfony and Laravel that try and modernize PHP dev workflow.