The brief history of Facebook open source:
- FB releases React under an oppressive licence that tells "woopsie, can't sue FB if you use React"
- a lot of money goes into making React popular to gain leverage from mass adoption
- VMware bans React in their company
- FB releases Flux to bring state management. It flops. Replaced by what some Russian student wrote in several evenings (Redux)
- Preact is released. It's faster than React, and it has MIT licence. Vue beats React in GitHub stars.
- Under mass pressure, FB changes React's licence to MIT. Initial plan to gain leverage fails spectacularly.
- FB releases Flow Types. It flops. Replaced by TypeScript.
- FB releases their own app market for React Native. It flops.
- FB releases Relay. It flops. Replaced by Apollo.
- FB tries to push React.Suspense for the whole JS landscape to obey and comply to how it works. Community says "Fuck You".
- FB releases react-native-web. It flops.
- Web Components are out in all browsers, adopted as a standard. React doesn't support them.
- Google releases Lit, a virtual DOM framework on top of Web Components to fuck with React. It's a massive success.
- React 18 is out. Still no Web Components support.
- (you are here)

Life as a homeless developer.

I'm a lil brainsick but homelessness makes you that way.
I started writing software as a hedge against an old injury i had from my teen years. I have a unique condition leaving me with limited use of my hand as such any jobs like cashier call center and they like are of limits to me, i can't hold change because my hands don't bend flat, and to much typing is excruciating. Therefore being adev should get the most bang for the buck that I have left. Ive been doing this for 12 years. Well it's all bullshit and unicorns. I can't get a job to save my life. All i get is calls from recruiters wanting a full stack retard. I'm an erlang developer for about 5 years, c# php no i can't do Photoshop or frontend gay as colors because it's a different skillet. Oh but trumpy says we're at the lowest unemployment ever, ya because we're all homeless and companies are still looking for unicorns, they don't exist just like the fake jobs which is the real fake news. In reality if a company wants you its because their dev left and you are to fix their broken shit, which never worked in the first place thus cannot be fixed besides I'm not a plumber. In my opinion many companies nowadays are run by liberal sjw children who don't value your time but want the product now, spoilt. Recruiters are the worst, gimme money because i touched your resume. I'd rather just kill myself than try to appease some fucking retarded children. Its so awesome to live in a tunnel while my skills entropy while i have 160 self published github repos, know many programming languages and be told your have no value. its those same children that dont understand the flow of money or value loyalty, claim we have all these jobs but no skillid employees, so they can bring in more visa overstayers, underpay them and claim record profits, the more you pay forieners my countries money the less there is to go around in the society leading to disenfranchised people like me, and you wonder why there's so many shootings in il. How long can i endure homelessness before i start becoming a criminal? Soon i will have no other option. You employers had a choice but I'm going out with a bang.

Holy fuck this new GitHub feature is amazing!!!
It's called GitHub Actions and you can easy automate your work flow using a simple graphical editor!
I need to test this out right fucking now!

Let's have some puntastic cheesy coding pickup lines in the comments 🌝 " are you github ? I've always wanted to commit to you " that's my take .. ( and I know it's bad ) let the creativity flow :)

Serious question: If a highly intelligent being, better than humans, is about to code something, how would they probably do it?

Will they use the same concepts like control flow, iterations, types, operators, object inheritance, etc?

If they are quantum capable, how can they code with booleans when it can be both true and false at the same time? Will they code truthy and falsy with another dimension like time-space temporality?

Do their code simultaneously modify the hardware or bio-hardware as it iterates over the outcome of the code?

Does input and output even relevant to them?

How do they represent infinites?

Do they have similar github workflows or they telepathically update the source code?

Do they embed their program in their DNA? Then pass to offspring the codes they already created?

Do they code using a language or do they use some frequencies and material science that simultaneously show real world output?

And do they have their version of devRant?

Made my first open source contribution today. 6 months into my degree. It was just editing a README with a proper description of the game that was created but good practice to get more familiar with the flow and usage of everything in Github.

What I'm doing now, writing a JS library for a simple kitchen timer (like, something that can be wound up, is ticking, can be paused, etc). Here's a list of neat stuff I've learned:

Polyfilling as a lib author (I decided against it).
Packaging the lib (using Rollup, ES6 modules are totes cool).
Using flow to add static typing in strategic places (started appreciating types in JS since reading up on functional programming).
Modelling state and transitions using an explicit state machine. (Fucking finally. There's usually an implicit state machine somewhere, only spread out all over the app...)
Using mostly side-effect free methods, being very explicit about when and why things are mutated).
Test-first/TDD (ish) using Jest and the awesome Wallabyjs.
Freeing up mental capacity by letting Prettier format my code for me (it was hard to let go but totally worth it).
Started using git.

Did all work on Ubuntu after pretty much a lifetime of Windows (initially to separate work from gaming) and finally swapped MS Visual Studio for Atom.

When it's finished I'm going to publish it on GitHub, which will also be a first for me. Might try out some CI platform while I'm at it.

tl;dr: wrote some js, felt good

To me this is one of the most interesting topics. I always dream about creating the perfect programming class (not aimed at absolute beginners though, in the end there should be some usable software artifact), because I had to teach myself at least half of the skills I need everyday.

The goal of the class, which has at least to be a semester long, is to be able to create industry-ready software projects with a distributed architecture (i.e. client-server).

The important thing is to have a central theme over the whole class. Which means you should go through the software lifecycle at least once.

Let's say the class consists of 10 Units à ~3 hours (with breaks ofc) and takes place once a week, because that is the absolute minimum time to enable the students to do their homework.

1. Project setup, explanation of the whole toolchain. Init repositories, create SSH keys for github/bitbucket, git crash course (provide a cheat sheet).
Create a hello world web app with $framework. Run the web server, let the students poke around with it. Let them push their projects to their repositories.
The remainder of the lesson is for Q&A, technical problems and so on.

Homework: Read the docs of $framework. Do some commits, just alter the HTML & CSS a bit, give them your personal touch.
For the homework, provide a $chat channel/forum/mailing list or whatever for questions where not only the the teacher should help, but also the students help each other.

2. Setup of CI/Build automation. This is one of the hardest parts for the teacher/uni because the university must provide the necessary hardware for it, which costs money. But the students faces when they see that a push to master automatically triggers a build and deploys it to the right place where they can reach it from the web is priceless.
This is one recurring point over the whole course, as there will be more software artifacts beside the web app, which need to be added to the build process. I do not want to go deeper here, whether you use Jenkins, or Travis or whatev and Ansible or Puppet or whatev for automation. You probably have some docker container set up for this, because this is a very tedious task for initial setup, probably way out of proportion. But in the end there needs to be a running web service for every student which they can reach over a personal URL. Depending on the students interest on the topic it may be also better to setup this already before the first class starts and only introduce them to all the concepts in a theory block and do some more coding in the second half.

Homework: Use $framework to extend your web app. Make it a bit more user interactive with buttons, forms or the like. As we still have no backend here, you can output to alert or something.

3. Create a minimal backend with $backendFramework. Only to have something which speaks with the frontend so you can create API calls going back and forth. Also create a DB, relational or not. Discuss DB schema/model and answer student questions.

Homework: Create a form which gets transformed into JSON and sent to the backend, backend stores the user information in the DB and should also provide a query to view the entry.

4. Introduce mobile apps. As it would probably too much to introduce them both to iOS and Android, something like React Native (or whatever the most popular platform-agnostic framework is then) may come in handy. Do the same as with the minimal web app and add the build artifacts to CI. Also talk about getting software to the app/play store (a common question) and signing apps.

Homework: Use the view API call from the backend to show the data on the mobile. Play around with the mobile project to display it in a nice way.

5. Introduction to refactoring (yes, really), if we are really talking about JS here, mention things like typescript, flow, elm, reason and everything with types which compiles to JS. Types make it so much easier to refactor growing codebases and imho everybody should use it.
Flowtype would make it probably easier to get gradually introduced in the already existing codebase (and it plays nice with react native) but I want to be abstract here, so that is just a suggestion (and 100% typed languages such as ELM or Reason have so much nicer errors).
Also discuss other helpful tools like linters, formatters.

Homework: Introduce types to all your API calls and some important functions.

6. Introduction to (unit) tests. Similar as above.
Homework: Write a unit test for your form.

(TBC)

Dear Web developers,
I'm looking to boost my skills and improve work flow. I was wondering what sort of tools, editors or platforms would you recommend? I currently use wordpress, php, jquery, sass, react, node and laravel.

I've heard about awesome ways where you can monitor project changes, something like github but with gui for design drafts and stuff.

Also I heard about good online platform for Web development, something like online sublime text where all your files are saved within cloud platform. I'm looking for something that will unify my work throughout different work places.

Lastly, are there any good sites or new technologies that are fairly popular and good to learn or research?

I scratched my head when GitHub gave a name ("Flow") to a normal workflow of git. Anyone else?

What's your team's best practice when using JIRA (on premises or cloud) and VSTS or GitHub?

Who manages issues/tickets and are they duplicated in both locations? Is one for PM only and other for Devs??

We have both tools and I'm trying to figure out a workflow that doesn't kill devs and PMs.

We have Office 365 so I heavily use MS Flow to help (Jira bug turns into vsts work item) etc, but any insight from anyone who has a similar setup would be appreciated!

Wasted a day fighting the breaking changes and new bugs over at Google Cloud Build's GitHub integration (alpha)... I had a good CI/CD flow that is broken now because of the change... anyway, I will switch over to Circle CI... have had enough of alpha bugs for the next few months... Google Cloud Build does have an attractive pricing (free 120 build minutes per day) and a whopping 10 concurrent builds limit... but it is only supported by the community and you don't get a lot of active developers feedbacks...

I have been using CakePHP 1.3 and 2.x fore some years. I built two custom platforms on them that we used for almost every project at work, and also some of my freelance ones.

We've built all kind of stuff, from basic CMS to large scale CRM/ERP systems, and it held it's own!

But now I wanna build another one! :D

I wanna build a platform on CakePHP 3.x fore sume time at work, but the constant flow of projects leaves little time for this.

And I am not talking about the shitty stuff like the sorry attempts you can find oh GitHub right now, that I never even managed to use once for a real project (I really tired!), I am talking about a real platform, for real world projects, with a real world interface, and real world functionallity, for real world use cases!

I was thinking to start an open source project, but I never managed one so I have some concerns...

Like it will not get any contributors and I will eventually do it on my own anyway, or like it WILL get traction and I will not be able to manage the project, or the community.

I am the head of the dev dept at work, but open source seems like a whole new ball game for me...

Anyway, what do you people think? Would you work on something like that? Would you use it? Should I create a GitHub project and add a collab? Or is it doomed already?