214 reputation
19
bio website github.com/vpereira
location Delaware
age 34
visits member for 1 year, 8 months
seen Apr 19 at 19:15

Developer and Security analyst


Apr
19
awarded  Commentator
Apr
19
comment Make a monolithic architecture in something modular
IMO there is no difference in maintaining code with dependency injection or inheritance. Why you think that DI is better? As you described, you should use inheritance.
Apr
9
comment Make a monolithic architecture in something modular
why Dependency Injection? What you are describing looks like a classical inheritance pattern. RequestDetailsForServiceOne is-a Request and RequestDetailsForServiceTwo is-a Request..
Aug
10
awarded  Yearling
May
21
comment Is it advisable to ask employees to create 'work' GitHub accounts?
beside, this feeling that: " it's physically here, it's better" even if everybody has the root password of a do-every-thing server is like to think that is better do put your whole saving under your pillow
May
21
comment Is it advisable to ask employees to create 'work' GitHub accounts?
to have github enterprise, than better gitlab. the big advantage to have everything in the cloud is to avoid the whole indirect costs (net admin, backup, servers, vpn and internet links always available if home office is an option and etc)
May
21
comment Is it advisable to ask employees to create 'work' GitHub accounts?
@BorisYankov the work account may be harder to compromise, if you don't have any public activity and the login has no relation with your name. It's security by obscurity, but it for sure helps. You can create a workflow that all emails sent by github are as well sent to the development team leader, etc. Another point: As work account you can decide and even do due diligence, auditing accounts and see if they are compliance with what was agreed between company and employee. A third important point: as soon as the user quit his job, you can take over his account.
May
21
awarded  Editor
May
21
comment Is it advisable to ask employees to create 'work' GitHub accounts?
well, if for example, an account is compromised, and we, some how discover that the password was abc123, we can "responsibilize" the employee. I don't see a problem here. Another point: where is written that I ENFORCE it? I wrote it must (now I updated to should)...
May
21
revised Is it advisable to ask employees to create 'work' GitHub accounts?
added 3 characters in body
May
21
awarded  Critic
May
21
awarded  Citizen Patrol
May
21
comment Is it advisable to ask employees to create 'work' GitHub accounts?
well you are saying that if you are not able to technically enforce something, you are not enforcing it. I'm saying that if, the a employee reads the security policy and if he sign it, knowing the consequences, it is an enforcement.
May
21
answered Is it advisable to ask employees to create 'work' GitHub accounts?
Feb
28
awarded  Caucus
Aug
14
comment QoS implementation algorithm
definitely i didn't discard it :-)
Aug
14
comment QoS implementation algorithm
the difference is that my application will be running as first hop of a network not in a backbone. I think the paper is related with high-speed networks and i'm sitting on the edge of the network.
Aug
14
awarded  Supporter
Aug
14
comment QoS implementation algorithm
i will check it, thanks
Aug
14
awarded  Student