This is exactly what we do at my place.


Trying to move to this workflow - as a stepping stone to CI/CD. Do you implement dead code in step 3 and then wire it together as the last step e.g. duplicating features during the crossover, then deleting the old feature/duplicated code/feature flags with something like below:



newFeature either being pulled from a table or actually in the application code.

Trying to understand how to do this eloquently as it seems hard to manage in our current workflow.

We might do something like your example if we were going to ship a feature in multiple stages, so that there would be releases where it was partially implemented. More typically we review and merge PRs into a feature branch apart from the "next release" branch and we might tolerate some things being in a partially implemented state in the feature branch.

We found config-driven switches of big blocks of code useful when making big changes that might need to be reverted. As long you have the discipline to go back and rip them out once you're sure you're not going back.

Also A/B testing with separate code bases. But some of the time that just wasn't feasible.

The part about ripping them out can't be emphasized enough. I've seen some pretty ugly codebases where that little detail was neglected.

Yeah, I guess in that example it probably doesn't make sense to separate

and we'd probably do it with feature flags. Basically what suzzer mentioned - configuration that can be read by the code to figure out which path should be taken. Common things we can do with ours is:

* Turn a feature on/off for specific customers
* Turn a feature on/off for a specific set of customers
* Turn a feature on/off for a random percentage of all of our customers

We had entire directory structures of old JSPs that everyone was 99.9% sure wasn't used, but still too afraid to rip them out. Terrible situation - especially when the only real source of truth for everything the site actually does was to trace the code.

Well things are flying fast and furious now with the job search.

ZipRecruiter seems to be a bot btw that recommends a lot of dumb jobs, or good jobs that are really just generic recruiter honeypots. Indeed and hired.com seem legitimate.

I've been able to narrow things down to most likely:

1) Not having to drive to Santa Monica
2) Coming in to a small company with a chance to build something from the ground up
3) Wearing a lot of hats, learning more DevOps (which I totally could and should have done with the startup side job, but they pissed me off so much I let the other guy do it)
4) Maybe learning Go, React or Vue
5) Salary demands mostly met
6) Possibly tele-commuting several or most days a week

One thing that bugs me is I'm talking to 3 recruiters and they all keep pimping me for if I'm talking to anyone else. Like sure they would tell me if they're pushing other clients to the same jobs as me.

Two of the recruiters found me before even posting all this stuff. I assume from me updating my linkedin profile (which I thought might happen).

Also I can see the handwriting on the wall that React will be as uncool as Angular in a year or so, replaced with Vue. All the cool startups are doing Vue. Angular might as well be COBOL. Lol front-end frameworks.

I'm currently learning go. We (frontend team) are migrating our codebase to vue from knockout. Dev (backend team) are moving a lot of php endpoints into go. The thing that surprises me is how often people seem to think

Its like... if you were **** at PHP then simply doing stuff in Go instead doesn't automatically make it better. Some of our apis done in go are still quite terrible. One allows you to query the entire table (last i checked, 7200 rows) is an example of that.

Im hoping that, before I move on to a new company, I'll be able to do a bit of work in go. The one thing we don't have right now are any websocket endpoints. Hopefully, that will be my one go project before I leave.

Suzzer you should come work for me in giant fortune 100 dinosaur company and um be a JSX monkey. Or work on the python api! Exciting.

LA?

MN

Can I work remote for the 7 months of winter and the 1 month of biting gnats and bird-sized mosquitos?

Does anyone know how indeed/stackoverflow/etc work with the dates on their job listings?

I will see a job listing that is '3 days old' but I have been seeing it for like 3 months straight. Is the company refreshing the listing? Does it refresh automatically?

It’s a cat and mouse game between job boards and companies posting jobs. The companies want their jobs to look fresh, and job boards don’t want people to game the system and bump up their jobs by reposting. But then, some jobs are kind of evergreen. Like, Amazon is never going to stop hiring java developers, and those posts shouldn’t be downgraded in the rankings because it’s months old. So it’s a tricky problem.

In conclusion, it depends. The single most useless answer to any question.

I’m guessing you’re one of those guys who thinks he can build a job board over a weekend and wondering what they’re doing with hundreds of engineers.

if companies are doing it themselves then i guess it's not really a big deal because it means that they are still hiring. the concern is if the sites are doing it themselves, it's being done automatically or companies are doing it just to stockpile resumes in preparation of eventually hiring someone.

more or less.

but i was also thinking it would be cool to scrape all the job boards + local slacks + meetup, etc and show listings for true freshness.

Pretending I'm a moron for a second - how do I find and sign up for my "local slack"? Thanks.

I would also like to know for a friend.

Is your concern that the 2 month old posting is not actually for an open position? You realize the companies have to pay for the traffic, right? And it's not cheap. In fact, some pricing plans for job posts are pay-per-click, so posting a job with no intention of hiring would be pretty silly. Don't submit your resume to companies that are intermediaries or recruiting agencies, and you should be fine.

what city do you live in? i will try to find it for you.

Here is the slack channel for Saint Paul, MN Angular.

https://angularmn-slack.herokuapp.com/

Here is the Javascript Slack

Find us on Slack: javascript-mn

Los Angeles Java Script

Join js.la on Slack.

46 users online now of 1191 registered.

go here and scroll down -> https://js.la/

so basically most of these slack channels revolve around tech meetups from meetup.com for your city